-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
ERROR: BrowserError: Could not start chrome with 3 tries #3895
Comments
Hi @kluslulu thanks for creating the issue! So Chrome version should not matter since we use the switch to turn off that check (and I hope that there are no breaking changes, that rarely happens). The easiest way to debug is to turn on the Chromedriver log, then I think we can get more/better info on what's going on. Can you try adding: Thanks |
Thanks for your replay @soulgalore: Thanks |
Hi @kluslulu hmm it just says Chromedriver 105 and nothing more. Can you upgrade to latest sitespeed.io (it will upgrade Chromedriver) and see how that works? Best |
Hi @soulgalore : I saw that the version of the changelog has reached 28.1.0 But I check all the versions through the npm command line: 'npm view sitespeed.io versions', the highest version is 26.0.0. And my local version is already the latest version Installed v28.0.1 directly and thrown an exception: Installed the latest version and goes to v26.0.0: Isn’t the highest version of sitespeed.io 26.0.0? Thanks~ |
I wonder if you have some proxy or something for npm? When I look locally on my machine:
And on https://www.npmjs.com/package/sitespeed.io?activeTab=versions I can also see the latest versions. |
Yes,you are right: Now I installed sitespeed.io28.0.1 successfully and generated a new log file: And the command line told me another error: Thanks for your patience~ |
Hi @kluslulu do you have any extensions installed for Chrome? If you have, can you try running with |
Hi @soulgalore: I tried this but still didn't work, and thrown a new exception: [2023-06-29 10:52:21] INFO: Versions OS: darwin 21.2.0 nodejs: v19.8.1 sitespeed.io: 28.1.0 browsertime: 17.11.2 coach: 7.2.1 Thanks~ |
Hi @soulgalore : I will check it carefully by myself and update here if I have a conclusion in the future. Thanks for your help and patience, Peter~ |
I think maybe it's a Chromedriver bug, looking at flathunters/flathunter#357 it seems others get the same problem as you on your Mac. I couldn't find any matching bugs at https://bugs.chromium.org/p/chromedriver/issues/list but if you have time, I can create simple test case just using Selenium/Chromedriver, and if you get the same problem there, it's easy to create a bug report and easier for the Chromedriver team to reproduce. |
Oh, I will be happy to cooperate with you to run your test cases. Thanks |
Thanks @kluslulu can you try this repo: https://github.com/soulgalore/selenium-test Clone it, then run npm install and run |
Thanks @soulgalore WebDriverError: disconnected: not connected to DevTools selenium-test.mp4 |
Did this got fixed? It seems like a Selenium/driver issue. I would try to run the latest version of sitespeed.io and see if it works. |
Always try with the latest version and make sure you run latest stable versions of the browsers. |
Could not start chrome with 3 tries
Hi,soulgalore
I installed sitespeed.io globally by npm about two or three months ago.
Everything is ok until the day before yesterday, the command line told me that chrome failed to start:
I thought maybe my chrome version didn't match, so I commissioned a colleague with the same chrome version as me to run it again, it's totally fine in his computer.
I'm confused and didn't find some effective solution.
I would appreciate it if you could give me some advice.
Here is some information about my environment:
Looking forward to your reply
Thank you
The text was updated successfully, but these errors were encountered: