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
gecko webdriver crash #821
Comments
I’m sorry, but I can’t tell what is wrong here unless you provide the full log from geckodriver. I suspect protractor is swallowing it, so you need to find some way to expose the stdout/stderr from geckodriver. I can tell from the stacktrace that it has something to do with creating a new Marionette (remote protocol) connection to Firefox. |
Will try to create a reproducer. |
Closing due to inactivity. I will happily reopen if reproducible steps are added. |
Couldn't create a reproducer. |
Hello, I have a similar stacktrace on :
Note : On Windows 10 everything is running well with FF 55 and gecko 0.18
|
@mmanach can you please provide a trace log? The output above is not enough. Thanks. |
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. |
Platform and application details
bitnami/minideb:stretch (docker image)
installed packages
dg-utils
libxi6
libgconf-2-4
libnss3
psmisc
fonts-liberation
libappindicator1
libgtk-3-0
libdbus-glib-1-2
libxt6
dbus-x11
x11vnc
xvfb
Firefox: 53.0.3 / 54.0.1 (both have the same behaviour)
selenium: 3.4.0
geckodriver 0.18.0
Steps to reproduce
Reproducable testcase:
sadly I don't have the steps.
the test is run by protractor.
the start command is
yarn run protractor
trace level log:
The text was updated successfully, but these errors were encountered: