You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following GoogleChrome/lighthouse#14488, I spent a long time trying to figure out the problem and what I've got so far is that if I run chrome -version in the bitbucket pipeline, it exits with code 133 (SIGTRAP).
Presumably, this is related to memory - but that's a different story.*
What I think would have helped me figuring out the problem earlier is if chrome-launcher also logged the exit code instead of just the (empty) log file (I'm quoting the output from that issue here):
Tue, 01 Nov 2022 21:29:56 GMT LH:ChromeLauncher:verbose created /tmp/lighthouse.6FOIZ8v
Tue, 01 Nov 2022 21:29:56 GMT LH:ChromeLauncher:verbose Launching with command:
"/opt/atlassian/pipelines/agent/build/vendor/node_modules/chromium/lib/chromium/chrome-linux/chrome" --disable-features=Translate --disable-extensions --disable-component-extensions-with-background-pages --disable-background-networking --disable-component-update --disable-client-side-phishing-detection --disable-sync --metrics-recording-only --disable-default-apps --mute-audio --no-default-browser-check --no-first-run --disable-backgrounding-occluded-windows --disable-renderer-backgrounding --disable-background-timer-throttling --disable-ipc-flooding-protection --password-store=basic --use-mock-keychain --force-fieldtrials=*BackgroundTracing/default/ --remote-debugging-port=43043 --disable-setuid-sandbox --user-data-dir=/tmp/lighthouse.6FOIZ8v --headless --disable-gpu --no-sandbox about:blank
Tue, 01 Nov 2022 21:29:56 GMT LH:ChromeLauncher:verbose Chrome running with pid 4519 on port 43043.
Tue, 01 Nov 2022 21:29:56 GMT LH:ChromeLauncher Waiting for browser.
Tue, 01 Nov 2022 21:29:56 GMT LH:ChromeLauncher Waiting for browser...
<snip>
Tue, 01 Nov 2022 21:30:21 GMT LH:ChromeLauncher Waiting for browser.......................................................................................................
Tue, 01 Nov 2022 21:30:21 GMT LH:ChromeLauncher:error connect ECONNREFUSED 127.0.0.1:43043
Tue, 01 Nov 2022 21:30:21 GMT LH:ChromeLauncher:error Logging contents of /tmp/lighthouse.6FOIZ8v/chrome-err.log
Tue, 01 Nov 2022 21:30:21 GMT LH:ChromeLauncher:error
Unable to connect to Chrome
*if you have any ideas, please do tell, I'm also a bit stuck there - I tried it with the following args to no effect: --headless --disable-gpu --no-sandbox --disable-dev-shm-usage --no-first-run --disable-setuid-sandbox --disable-infobars --window-size=1366,768 I found a solution, I simply downgraded the chrome version to 107 (latest stable on linux). The root cause is still a mystery..
The text was updated successfully, but these errors were encountered:
Following GoogleChrome/lighthouse#14488, I spent a long time trying to figure out the problem and what I've got so far is that if I run
chrome -version
in the bitbucket pipeline, it exits with code 133 (SIGTRAP).Presumably, this is related to memory - but that's a different story.*
What I think would have helped me figuring out the problem earlier is if chrome-launcher also logged the exit code instead of just the (empty) log file (I'm quoting the output from that issue here):
*
if you have any ideas, please do tell, I'm also a bit stuck there - I tried it with the following args to no effect:I found a solution, I simply downgraded the chrome version to 107 (latest stable on linux). The root cause is still a mystery..--headless --disable-gpu --no-sandbox --disable-dev-shm-usage --no-first-run --disable-setuid-sandbox --disable-infobars --window-size=1366,768
The text was updated successfully, but these errors were encountered: