Since the upgrade my angular e2e tests started failing with following message.
I am using directConnect: true
and all my tests are using async/await.
It looks it is crashing and does not always crash at the same point in my tests - and I do have some test running successfully. Disabled sharding as well.
- Failed: unknown error: session deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
(Session info: headless chrome=83.0.4103.61)
(Driver info: chromedriver=83.0.4103.39 (ccbf011cb2d2b19b506d844400483861342c20cd-refs/branch-heads/4103@{#416}),platform=Linux 3.10.0-1127.el7.x86_64 x86_64)
UPDATE: 6/1/2020 After adding more shared memory (finding CI runners that have more memory) this problem is gone. Still leaves the problem in a "mystery mode".
Update 6/2/2020:
Chrome Flags
'headless',
'verbose',
'w3c=false',
'disable-infobars',
'window-size=1440x1080',
'disable-dev-shm-usage',
'disable-gpu',
'incognito',
'disable-extensions',
'disable-plugins',
'no-sandbox'
If your computer is low on RAM (which is often a problem due to Chrome's high memory usage), it may cause websites to crash. Try closing all tabs you're not using, pausing any Chrome downloads, and quitting any unnecessary programs running on your computer.
There could be something wrong with your Chrome profile that's causing problems. Uninstall Chrome and make sure to check the box to delete browsing data. Then reinstall Chrome. Uninstall and reinstall extensions.
From the “Menu” button in the upper-right corner of the Chrome window, choose “More Tools” > “Clear browsing data…“. Press “CTRL” + “Shift” + “Delete” keys in Windows or Linux, or “Command” + “Shift” + “Delete” keys on MacOS. Select “Menu” > “Settings” > “Advanced” > “Clear browsing data…“.
Here are some of the factors that could be causing the Chrome browser to crash: You have had accidentally installed malware on the browser or the computer; You have opened too many tabs and websites on the browser, resulting it to lower its efficiency; There is something wrong with the network adapter of your PC.
I'm using chrome headless in podman and I've run into the same issue, here's what seems to work for me:
I needed the option in the past because it was impossible to change default /dev/shm size in a proprietary cloud software I'm using, looks like it's broken in the last chrome release. The funny thing is - chrome also runs much faster after the changes
same here, after every update they want us to suffer, to find a pass to buddhism
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With