-
Notifications
You must be signed in to change notification settings - Fork 26
[🐛 Bug]: Session crashed #67
Comments
How can we reproduce this? |
I don't understand the question exactly what we will reproduce. @diemol |
You are asking:
It is hard to know. The best would be to have a way to reproduce the situation you are having to know why this could happen. |
Every time it runs, it gives the same error after a while. I also provide the source, but the error does not change, the session crashes. @diemol |
I am not sure how we can help, you should know when the crash happens during the execution. |
If the number of links I scrape is low, it works very well, but when the number of links increases, it crashes. Also, could it be related to resource consumption? Memory usage is constantly increasing, shouldn't it remain stable at some point? |
You probably need to measure those items, CPU and RAM to find a correlation between the crash and resource usage. |
mehmetturkmen@192 ~ % /usr/local Traceback (most recent call last): This is the output of the code when debugging |
I am sorry, we cannot do much with your information. Just so you know, we cannot troubleshoot your environment or code. We can only troubleshoot bugs that have a way to reproduce them. If you need help to understand your issue, you should head to our community resources: https://www.selenium.dev/support/. |
Could this be related to https://issues.chromium.org/issues/41494493 (fixed in Chrome v122)? We also experienced crashes after running Test-Suites with a larger amount of tests. Running single tests was perfectly fine. Downgrading to 4.9.1 (with Chromedriver v113) resolved the issue for us. |
This solution worked for me. I encounter the same problem in all current versions above Chrome 120.0. In Chrome 120, resource consumption remains constant and does not constantly increase. So thank you for the solution you offered. @sf-job |
Why is downgrading a good solution? Are your users also downgrading to Chrome 113? |
What happened?
I am doing web scraping by running the Python code on the selenium grid. While it works fast and well, the session suddenly crashes and gives an error before it can pull the whole thing. What is the reason for this?
I get errors with both startup commands
Command used to start Selenium Grid with Docker (or Kubernetes)
Relevant log output
Operating System
macos M1 Pro
Docker Selenium version (image tag)
seleniarm/standalone-chromium:latest
Selenium Grid chart version (chart version)
4.18.0
The text was updated successfully, but these errors were encountered: