selenoid
selenoid copied to clipboard
page crash
very many requests on chrome, page crash.
1、docker-compose.yml
version: '3'
services:
selenoid:
image: "aerokube/selenoid"
network_mode: bridge
restart: always
ports:
- "4444:4444"
volumes:
- "/home/ubuntu/compose/selenoid/:/etc/selenoid/" # assumed current dir contains browsers.json
- "/var/ubuntu/selenoid/video:/opt/selenoid/video/" #
- "/var/ubuntu/selenoid/logs/:/opt/selenoid/logs/"
- "/var/run/docker.sock:/var/run/docker.sock"
- "/var/jenkins/workspace:/opt/docker/fileDownloadLocation"
environment:
- OVERRIDE_VIDEO_OUTPUT_DIR=/var/ubuntu/selenoid/video
command: -limit 20 -service-startup-timeout 2m -timeout 5m -session-attempt-timeout 2m -retry-count 3 -enable-file-upload -log-output-dir /opt/selenoid/logs
selenoid-ui:
image: "aerokube/selenoid-ui:latest-release"
network_mode: bridge
restart: always
links:
- selenoid
ports:
- "8080:8080"
command: ["--selenoid-uri", "http://selenoid:4444"]
video-recorder:
image: "selenoid/video-recorder:latest-release"
network_mode: bridge
restart: always
vnc:
image: "selenoid/vnc:chrome_100.0"
network_mode: bridge
restart: always
2、browser.json
{
"chrome": {
"default": "98.0",
"versions": {
"98.0": {
"image": "selenoid/vnc:chrome_98.0",
"port": "4444",
"path": "/",
"volumes": ["/var/jenkins/workspace:/opt/docker/fileDownloadLocation"]
},
"99.0": {
"image": "selenoid/vnc:chrome_99.0",
"port": "4444",
"path": "/",
"volumes": ["/var/jenkins/workspace:/opt/docker/fileDownloadLocation"]
},
"100.0": {
"image": "selenoid/vnc:chrome_100.0",
"port": "4444",
"path": "/",
"volumes": ["/var/jenkins/workspace:/opt/docker/fileDownloadLocation"]
}
}
},
"firefox": {
"default": "79.0",
"versions": {
"79.0": {
"image": "selenoid/vnc:firefox_79.0",
"port": "4444",
"path": "/wd/hub"
}
}
},
"safari": {
"default": "14.0",
"versions": {
"14.0": {
"image": "browsers/safari:14.0",
"port": "4444",
"path": "/"
}
}
},
"opera": {
"default": "70.0",
"versions": {
"70.0": {
"image": "selenoid/vnc:opera_70.0",
"port": "4444",
"path": "/"
}
}
}
}
@carl-pki try to increase shmSize
parameter in browsers.json
. https://aerokube.com/selenoid/latest/#_other_optional_fields
I tried, but the bug was exist !
@carl-pki then this is a bug of your app.
I also thought about it but it works in selenoid/vnc:chrome_98.0, but it crashes in selenoid/vnc:chrome_99.0, selenoid/vnc:chrome_100.0
Faced the similar issue. Updated Selenoid to the latest version, updated chrome to version 100.0 and got 95% of tests failed because of crashed pages. We also use vnc, but I tried without it and the issue still exists. For some reason chrome 100 crashes during the testing while chrome 98 works perfect
Small update. Check the session logs and there were a lot of errors "Failed to load resource: net::ERR_INSUFFICIENT_RESOURCES". I guess this provoked the browser page to be crashed. Found the same question on stack with wdio. https://stackoverflow.com/questions/71752416/browser-is-crashing-in-ci-after-updating-chrome-to-100-i-see-error-err-insuffic Being run locally tests don't fail on Chrome 100.
I have same problem since Chrome 99. and 100. Work fine with Chrome 98.
Any progress on your side to fix or find a workaround?
We have a similar errors with Chrome 104.0.5112.79
- "Failed to load resource: net::ERR_INSUFFICIENT_RESOURCES".
Local run gives no errors.
The same is true for the new version of Chromedriver 105.0.5195.52. The behavior is the same as reported previously. The page enter a loop with the ERR_INSUFFICIENT_RESOURCES and finally, the test goes as a KO.
This is happening with all the last versions on Chrome and was not happening with Chrome 98 with the same code and same page. So is not a bug on our side.
The already mentioned "shmSize parameter" is not working we try to give 4 times the space and still have the same behavior.
Anyone knows a workaround to be able to update chromedriver from 98 to some more modern version?
We've recently fixed this in Chrome images: https://github.com/aerokube/images/issues/544 Try to repull Chrome 105.0 image and check whether it helps.
My team had this issue also with the chrome 99 release and it appeared on one of our older projects that we test, we managed to solve this by using the chrome option "--disable-dev-shm-usage", with this flag chrome doesn't crash and it is working fine, same goes for all the newer versions of chrome.
We just moved to chrome 106 and this flag still works for us.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.