Corion / WWW-Mechanize-Chrome

automate the Chrome browser
https://metacpan.org/release/WWW-Mechanize-Chrome
Artistic License 2.0
30 stars 12 forks source link

Chrome/Chromium v97 closes CDP websocket while setting up a new instance #64

Closed Corion closed 2 years ago

Corion commented 2 years ago
Launching browser at scripts/vidconf-jitsi.pl line 64.
2022/01/20 17:38:50 Spawning for websocket $VAR1 = [
          '/bin/chromium',
          '--remote-debugging-port=0',
          '--remote-debugging-address=127.0.0.1',
          '--user-data-dir=/tmp/0cwJVdJ9YF',
          '--profile-directory=/tmp/0cwJVdJ9YF/profile/test1',
          '--enable-automation',
          '--no-sandbox',
          '--safebrowsing-disable-auto-update',
          '--disable-background-networking',
          '--disable-breakpad',
          '--disable-client-side-phishing-detection',
          '--disable-component-update',
          '--disable-hang-monitor',
          '--disable-prompt-on-repost',
          '--disable-sync',
          '--disable-translate',
          '--disable-web-resources',
          '--disable-default-apps',
          '--disable-infobars',
          '--disable-popup-blocking',
          '--disable-gpu',
          '--disable-save-password-bubble',
          'about:blank'
        ];
2022/01/20 17:38:50 Spawned child as 1814216, communicating via websocket
2022/01/20 17:38:50 [[[1814257:1814257:0120/173850.697653:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is]]
2022/01/20 17:38:50 [[[1814216:1814216:0120/173850.699659:ERROR:profile_manager.cc(888)] Cannot create profile at path /tmp/0cwJVdJ9YF//tmp/0cwJVdJ9YF/profile/test1]]
2022/01/20 17:38:50 [[[1814216:1814216:0120/173850.699691:ERROR:profile_manager.cc(1759)] Cannot create profile at path /tmp/0cwJVdJ9YF//tmp/0cwJVdJ9YF/profile/test1]]
2022/01/20 17:38:50 [[]]
2022/01/20 17:38:50 [[DevTools listening on ws://127.0.0.1:43339/devtools/browser/8010f652-877a-413f-966d-6fbf70f0ae46]]
2022/01/20 17:38:50 Found ws endpoint from child output as 'ws://127.0.0.1:43339/devtools/browser/8010f652-877a-413f-966d-6fbf70f0ae46'
2022/01/20 17:38:50 Using endpoint ws://127.0.0.1:43339/devtools/browser/8010f652-877a-413f-966d-6fbf70f0ae46
2022/01/20 17:38:50 Connecting to ws://127.0.0.1:43339/devtools/browser/8010f652-877a-413f-966d-6fbf70f0ae46
2022/01/20 17:38:50 Connected to ws://127.0.0.1:43339/devtools/browser/8010f652-877a-413f-966d-6fbf70f0ae46
2022/01/20 17:38:50 Sent 'Target.getTargets' message $VAR1 = '{"method":"Target.getTargets","params":{},"id":1}';
2022/01/20 17:38:50 Replying to 1 $VAR1 = {
          'result' => {
                        'targetInfos' => []
                      },
          'id' => 1
        };
2022/01/20 17:38:50 Sent 'Target.createTarget' message $VAR1 = '{"params":{"url":"about:blank"},"method":"Target.createTarget","id":2}';
2022/01/20 17:38:50 Connection closed

Obviously, the connection should not be closed. It seems to be unlikely that this is a heartbeat issue. Further investigation is needed.

Corion commented 2 years ago

The profile directory passed in --profile-directory resp. the profile option must be a single directory name, not a full path!