Bug P3
Status Update
Comments
de...@gmail.com <de...@gmail.com> #2
Yes, I can confirm seeing this intermittently, starting with Chrome 132 + ChromeDriver 132
Appears both as WebDriverException & UnsupportedOperationException for us:
WebDriverException aborted by navigation: loader has changed while resolving nodes (Session info: chrome=132.0.6834.110)
UnsupportedOperationException aborted by navigation: loader has changed while resolving nodes (Session info: chrome=132.0.6834.110)
da...@gmail.com <da...@gmail.com> #3
Anybody knows any workaround for the issue?
Or we have to wait until google team resolve this?
Or we have to wait until google team resolve this?
st...@gmail.com <st...@gmail.com> #4
Just noted that running from linux terminal
- as root ==> no errors
- as www-data ==> gives error
What could have changed from 131 to 132+ to cause it?
- as root ==> no errors
- as www-data ==> gives error
What could have changed from 131 to 132+ to cause it?
Description
When I update to latest chromedriver version in my selenium grid sometimes I get this error when executing the tests:
OpenQA.Selenium.UnsupportedOperationException : aborted by navigation: loader has changed while resolving nodes
(Session info: chrome=132.0.6834.83)
When I restore the previous chromedriver version 131 everything is working fine again.
Anybody noticed the same error with latest version?
Thanks.