New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use Firefox + Remote Selenium + Geckodriver Server in a docker container - Cannot recover from Timeout loading page #1193
Comments
Thanks for the logs, but neither of them include the trace-level from geckodriver. Can you please attach some with the trace-level? |
oops! trace is on now @andreastt links are updated |
the memory setting as indicated here: #285 (comment) fixes the issue.
This ticket was opened to address the need for documentation here: https://bugzilla.mozilla.org/show_bug.cgi?id=1442356 |
@andreastt kubernetes users don't get access to this setting. so feel free to re-open this ticket if you feel like this can be avoided in the first place. |
kubernetes/kubernetes#28272 |
There is no way to get around that unless the above mentioned bug has been fixed. So this issue is a dupe of #285. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have run into an issue you think is related, please open a new issue. |
System
also tried a centos docker container, same issue
Testcase
Full reproducer available https://github.com/nddipiazza/geckodriver-issue1193-reproducer
I also repeated this test using non-headless firefox with XVFB. Same issue.
Steps are below how to use it:
Pull docker instance, run it, open a bash
Install prereqs and run the reproducer
Stacktrace and trace level logging
Log when program is run from docker: https://gist.github.com/nddipiazza/088b874b575f85b847a4468424cde925
Log when program is run from non-docker (ubuntumate 16, 64-bit):
https://gist.github.com/nddipiazza/08484d65f1e9b2e814d2aca575b518ea
Main stack of interest seems to be:
You can clearly see the non-docker version is able to recover from this timeout.
But when on docker, it will not recover.
I also tried this same test with Selenium + Chromium + Chrome Driver. seems not to have the issue. so it's not selenium itself as far as I can tell.
The text was updated successfully, but these errors were encountered: