geckodriver requires Microsoft MSVC runtime to be installed on Windows #1617
Comments
|
Could you please attach a trace-level log from geckodriver? Read more about reporting actionable bugs in our contribution guidelines. |
|
I've been running against this issue but just on a windows environment. |
Hi. However the strange things happen which it is actually runable and launched in my physical machine, and unable to launch the browser in my virtual machine |
|
That is not a trace-level log. |
Hi， |
|
Then what is the output of the process when you start it? |
i am actually getting all this log from selenium-webdriver: 12:08:16.467 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444 it stuck and prompted with error However same set up with my physical machine is working: |
|
any chance it is webdriver-manager issue instead of gecko driver ? |
|
We don’t track Selenium or chromedriver (your paste above contains references to |
|
i will close this issue first and raise it to to webdriver-manager team. As nothing related to geckodriver get printed. |
|
@Julioevm |
|
@bboycs I did not get this doing the same with version 0.24.0 so I assume the problem comes from the geckodriver.exe not starting and thus selenium not being able to connect to the new session. Installing Microsoft Visual C++ 2015 Redistributable Update 3 RC solved the issue: |
|
@Julioevm Thank you, this is the first valuable feedback we’ve gotten about the multitude of reports that geckodriver 0.25.0 has been problematic on Windows. With the 0.25.0 release we switched our build environment from cross-compilation on Travis/GitHub, to building it on Mozilla’s TaskCluster system. This means the binaries are produced in a different way and may require different dynamic libraries at runtime. I haven’t got time right now to look into this, but re-opening this issue to track this for the moment until we’ve clarified it’s fine to depend on the Visual C++ redistributable package. |
andreastt
changed the title
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
whimboo
changed the title
|
Anyone experiencing this issue can you please try the following:
Do the unsigned and/or test builds behave the same way, or are the test builds working fine without the redistributable package been installed? |
|
Depending on the system different DLLs seem to be missing when trying to launch geckodriver.exe: |
|
@st-schaefer is your reply based on my last comment from yesterday? If not please test those geckodriver builds. Thanks! |
|
Sorry, didn't try the test builds first. I just used the latest release build. Installing the MSVC Runtime helped on both machines. But now I uninstalled the MSVC Runtime and used both of your 64bit builds above (test build and usigned build) Both failed on my Win10 machine with a missing api-ms-win-crt-heap-l1-1-0.dll (which obviously is included in the Runtime as well). |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Thanks. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1584530 to get the dependency to the MSVC runtime removed. |
|
I haven't setup a windows box yet, but a colleague take a stab on that and might have fixed it. Could one of you please try one of the following test builds? win32: https://queue.taskcluster.net/v1/task/bYXQZvVsRuGhzmrVwj4r3w/runs/0/artifacts/public/build/geckodriver.tar.bz2 Thanks! |
I tried your 64bit version, and it worked for me on a machine, where the latest official build failed. Great! |
|
@st-schaefer thanks a lot for testing! We will get this patch landed shortly, and released as part of the upcoming 0.26.0 release hopefully this week. |
|
Is there any updates on 0.26.0 ETA? We are bundling GeckoDriver with one of our products, and while the workaround with manual VC++ runtime installation works, it feels a bit cumbersome especially for the new, less-techy, users. Thanks! |
|
Sorry, but even with the 0.26.0 release most likely being out tomorrow we weren't able to get this fix into the release without stopping to ship the signed builds. We hope that the remaining issue will be solved soon so that we can ship a 0.26.1 bug fix release soon. We are really sorry that this is causing trouble in some environments, so best might be to pin your version of geckodriver to 0.24.0 for now. |
|
In the meantime you will need to install MSVCRT on all your Windows test machines for geckodriver to work. |
whimboo
changed the title
whimboo
changed the title
|
@whimboo is there any ETA for v0.26.1? |
|
There’s no timeline, but you can track the progress of 0.27.0 in this bug: |
This comment has been minimized.
This comment has been minimized.
|
@Rameshwar-Juptimath, hard to say. What about installing the runtime and try again? Also please don't add such huge traces in a comment but attach a file in the future. Thanks. |
|
@whimboo Apologies for the huge trace. I did install runtime and it worked fine. I tried running geckodriver.exe before installing runtime and it did not run. After installing runtime, it worked fine. |
|
This issue appears to have been resolved in 0.27.0. |
|
Yes, it has. I simply forgot to close this issue. Thanks for pointing out. |
System
webdriver-manager: 12.1.6,
selenium server 3.141.59
Testcase
Stacktrace
The text was updated successfully, but these errors were encountered: