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.
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.
