WebDriverException: unknown error: Chrome failed to start: exited abnormally #4961
Comments
|
Report this issue to chromedriver project: https://sites.google.com/a/chromium.org/chromedriver/help |
|
Exp. the same issue. @PascalGit1 were you able to resolve his? |
|
@bondib sadly not i made a post on the chromedriver usergroup located here: |
|
Hello guys, I've been fighting with this issue for a long time, and just y'day I figure out how to make it gone and today I can run a 50 threads process calling selenium without seen this issue anymore and also stop crashing my machine with outofmemory issue with too many open chromedriver process.
this 4 items are the basic setting everyone would already knows, now comes the code, where all made a lot of difference to achieve the success: public class HttpWebClient { |
|
BTW, I found a workaround by starting chrome at --no-sandbox mode (which is notbthe bewt practice). So it's a permission issue.
…________________________________
From: Pascal <notifications@github.com>
Sent: Monday, November 20, 2017 3:05:44 PM
To: SeleniumHQ/selenium
Cc: Benjamin Bondi; Mention
Subject: Re: [SeleniumHQ/selenium] WebDriverException: unknown error: Chrome failed to start: exited abnormally (#4961)
@bondib<https://github.com/bondib> sadly not i made a post on the chromedriver usergroup located here:
https://groups.google.com/forum/#!topic/chromedriver-users/8yZDv_h8feg
but nobody has replied yet so im not sure if they are even looking at it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#4961 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/APcAfpfoGf7hhmsWNTE8RhuSF98kg3MJks5s4Xh2gaJpZM4QHLcJ>.
|
…rt: crashed" add the '--no-sandbox' option to Chrome based on the discussion in SeleniumHQ/selenium#4961 to avoid consistent test failures appeared lately
|
this is weird though. In one repo I use totally the same code with shippable for chromedriver and chrome itself as in another repo, and it's working fine without |
|
I had the same problem: roughly 1% of selenium tests failed with: This happened only when running multiple tests in parallel on the same server. The --no-sandbox option did not help me. However, for some reason option --single-process helped and the problem went away. I used this combination: But the problem occurred also with: |
|
Man, I noticed if I run selenium as super admin, then it doesn't work as the error message above. But if I run selenium without sudo, then it works. Maybe it will help you. God bless you :) |
|
People still having this issue and are desperate the only thing that seems to work is update to V2.35 It's not a great fix but it seems like it was the only thing that works for me. |
|
in which file do we need to put --no-sandbox? can someone here give me the example? |
|
@jaswennyhuangg in wdio.conf.js at least that’s where I use it with web driver.io . 🍺 |
OS:
Linux
Selenium Version: 3.5.3
Browser: Chrome driver V2.33 , chrome version 62.03
I'm running Selenium tests from jenkins on a linux machine. For this i'm using the latest chromedriver, when I run my tests about 90% will succeed but maybe 1 in 10 of the tests it will randomly fail with the following error:
Error:
When rerunning the same test it will usually succeed the 2nd try so im not sure how i can reproduce this consitantly. I have a maven project and it is setup like the follow:
Driver class:
Pom.xml dependencies:
Hopefully you can help me, if you need some chrome logs i will add these aswell but they are a bit long so I didnt add them yet.
The text was updated successfully, but these errors were encountered: