"Is anyone else having issues with Chrome Driver version 125.0.6422.142?"
Hey folks,
just updated to chrome driver version 125.0.6422.142 and it's been acting *weird*. Some tests are failing randomly, and I'm getting timeouts even with simple pages.
Anyone else facing this? Or is it just my setup?
Tried rolling back to the previous version and it works fine, so pretty sure it's this one.
Also, if you've found a fix, pls share!
Thanks!
---
(Word count: ~70)
Yeah, same issue here! Chrome driver version 125.0.6422.142 is causing random failures in my automation scripts too.
I checked the ChromeDriver release notes, and it seems like there might be a bug with certain page interactions.
For now, I’ve downgraded to 124.0.6367.91, and it’s stable. Maybe give that a shot?
Also, if you’re using Selenium, try adding explicit waits—sometimes that helps with the timeouts.
Ugh, glad it’s not just me. This version is *messed up*.
My tests were passing fine until I updated to chrome driver version 125.0.6422.142. Now they’re flaky as heck.
Found a thread on Stack Overflow where someone suggested clearing the browser cache and disabling extensions. Didn’t work for me, but maybe worth a try?
Let me know if you find a fix!
Hey! Had the same problem with chrome driver version 125.0.6422.142.
Turns out it’s a known issue in the Chromium bug tracker. Some folks are reporting it’s related to shadow DOM interactions.
If you’re dealing with shadow DOM, try using `driver.execute_script` to force clicks instead of the regular Selenium methods.
Otherwise, rolling back is the way to go for now.
Yep, chrome driver version 125.0.6422.142 is a nightmare.
My CI pipeline started failing randomly, and it took me forever to pin it down to this update.
Pro tip: Check your Chrome browser version too—sometimes mismatches cause weird behavior.
If you’re stuck, the Selenium Slack community has some active threads about this. Might find a workaround there!
Same boat! chrome driver version 125.0.6422.142 is breaking my headless tests.
Tried updating Chrome to the latest stable version, but no luck.
Found a temporary fix—adding `--disable-gpu` and `--no-sandbox` flags to the Chrome options. Not ideal, but it got my tests running again.
Hope they patch this soon.
Oh man, I thought I was going crazy. chrome driver version 125.0.6422.142 is *definitely* buggy.
My tests were timing out on simple pages too.
Weirdly, switching to GeckoDriver (Firefox) as a temporary workaround helped. Not a fix, but at least the tests pass.
Anyone know if Google’s acknowledged this yet?
Thanks for all the replies! Downgraded to 124.0.6367.91, and it’s working fine now.
Still weird that chrome driver version 125.0.6422.142 is so unstable.
Has anyone reported this to the Chromium team? I’ll dig into the bug tracker later.
Appreciate the tips—especially the shadow DOM workaround. Gonna test that next!
Yup, chrome driver version 125.0.6422.142 is causing issues for us too.
Our team noticed it’s particularly bad with dynamic content—like AJAX-heavy pages.
Try increasing the default timeout in your Selenium config. Also, make sure you’re not mixing implicit and explicit waits (that can make things worse).
If all else fails, downgrade and wait for a patch.
