Chrome 113 return error when checking existence of DOM

[dwee cs]

Hi,
i am getting error 
unknown error: unhandled inspector error: {"code":-32000,"message":"No node with given id found"}
when i checking the dom element existence with protractor API  after i dismiss it.
It used to work still in chrome 112. 

Attached with log 

[Dakshu Naidu]

I got a same issue today, but some times I am prompted with above error, and sometimes working, I am also on Chrome version 113

[Dakshu Naidu]

I got a same issue today, but some times I am prompted with above error, and sometimes working, I am also on Chrome version 113

On Thursday, May 11, 2023 at 3:13:06 PM UTC+5:30 dwee cs wrote:

[Tom Wilson]

We are getting the same problems under v112 tests worked fine but now they fail with this error. 

There does seem to be an open bug for the driver version and this exact error in the bug tracker here:  https://bugs.chromium.org/p/chromedriver/issues/detail?id=4440

[Jytesh Punjwani]

We are also getting this error from v113 it was working fine before. Getting this error at  SeleniumExtras.WaitHelpers.ExpectedConditions.<>c__DisplayClass21_0.<StalenessOf>b__0(IWebDriver driver)

[AOT]

Here too. I tried increasing timeouts for implicit, pageload and script, but no success.

BTW. Firefox w/geckodriver is a temp workaround for me.

[Sushant Vsic]

org.openqa.selenium.WebDriverException: unknown error: unhandled inspector error: {"code":-32000,"message":"No node with given id found"}

I am also same error from today..

[jongyoon kim]

tired of this issue. how are you all handling this issue?

2023년 5월 23일 화요일 오후 5시 6분 8초 UTC+9에 Sushant Vsic님이 작성:

[dwee cs]

I downgrade to chromedriver 112

--
You received this message because you are subscribed to a topic in the Google Groups "ChromeDriver Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/chromedriver-users/ziWgK92VNJY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/ddb109a3-2321-4c28-8502-bc13ca5ec656n%40googlegroups.com.

[Swapna Bhaskaruni]

how to downgrade if we are using webdriver manager

[Dante Soto]

I got exactly same question:   how to downgrade if we are using webdriver manager? if someone has accomplished that, please share. Thanks!

[Matthew Hibshman]

We're experiencing the same issue using CyberArk. CyberArk uses chromedriver to automate logins and every since mid-month Chrome 113/chromedriver 113 upgrade, having frequent periodic incidents of this preventing our sessions from logging in. Hoping fo ra fix but likely going to have to downgrade to 112.

[Dimple Patel]

Facing the same issue for chrome driver 114 version also. any body able to do any work around for this?

[Amir Mahgoub]

is there any solution how to solve it 

[Wisamul Haque]

A temporary fix is to add browser.refresh() at the point where this issue is coming. 

[Ory Zaidenvorm]

In C# we are working around this issue as follows:

1. Add an extension method to WebDriverException:

public static bool IsActuallyStaleElementException(this WebDriverException ex)
{
    if (ex.Message.Contains("unhandled inspector error"))
      {
             if (ex.Message.Contains("No node with given id found"))
                return true;
             else
                    return false;
}

2. In our framework, wherever we are handling  StaleElementReferenceException  , we use an additional try...catch(WebDriverException) and add a check for IsActuallyStaleElementException e.g.:

public class CommonExpectedConditions
{
    /// <summary>
    /// An expectation for checking that an element is either invisible or no longer present on the DOM.
    /// </summary>
    /// <param name="element">The locator used to find the element.</param>
    /// <returns><see langword="true"/> if the element is not displayed; otherwise, <see langword="false"/>.</returns>
    public static Func<IWebDriver, bool> InvisibilityOfElement(IWebElement element)
    {
        return (driver) =>

         {

            try

            {

                 return !element.Displayed;

            }

            catch (NoSuchElementException)

            {

               // Returns true because the element is not present in DOM. The

               // try block checks if the element is present but is invisible.

               return true;

            }

            catch (StaleElementReferenceException)

            {

               // Returns true because stale element reference implies that element

               // is no longer visible.

               return true;

            }

            catch (WebDriverException ex)

            {

               if (ex.IsActuallyStaleElementException())

                  // workaround for https://bugs.chromium.org/p/chromedriver/issues/detail?id=4440

                  return true;

               throw;

            }

         };

   }

}

Hope this is helpful!