Chromium

[Comment Deleted]

I get this error randomly on `driver.refresh()`

We're also getting this since upgrading to Chrome 99,. Nothing else changed on the app or the test, on our side.  

We're also getting this since upgrading to Chrome 99.

I get this error as well with Chromedriver and Chrome browser 99. I have the same code running on another machine with version 98 and have never seen this error.

Same problem here "unknown error: cannot determine loading status from target frame detached". randomly occuring

Been getting this error for the last few days after updating to Chrome 99. Nothing in my code changed but it is now no longer functioning

Same problem after updating to Chrome 99 on driver.get(). Same code with version 98 works perfectly

Same issue here with chromedriver and chrome 99, we're getting a ton of these failures:

- WebDriverError: target frame detached
- WebDriverError: element not interactable
- WebDriverError: unknown error: cannot determine loading status from target frame detached

all of them with v99:
  (Session info: chrome=99.0.4844.74)
  (Driver info: chromedriver=99.0.4844.51 (d537ec02474b5afe23684e7963d538896c63ac77-refs/branch-heads/4844@{#875}),platform=Linux 4.14.268-205.500.amzn2.x86_64 x86_64)

Same here, lots of errors on v99. I'm on macOS Catalina.

The error still seems to occur with the latest chromedriver (v100) and Chrome Beta (v100).

Hi saitdinc44@gmail.com
Can you please elaborate on how to reproduce the problem?
What is the page structure and where is the element you are waiting for?

Same problem here 'target frame detached". erroe while Im switching between the frames

+1

Still happens in chrome=100.0.4896.60

+1

I am also experiencing this issue. Using Pytest and Selenium. As soon as we updated Chrome and ChromDriver to V99 (Driver version 99.0.4844.51), we get about a 25% failure rate and error rate with our tests.

We're still struggling to get a consistent repro of this, but I wanted to confirm that the issue is still present on dev build 101.0.4951.7.

reply to mtrea@google.com  - still seeing on version 100.0.4896.60 - please fix this - breaking all of our automation

I don't know if this is helpful in any way, but I noticed there aren't real steps to reproduce here. This is what I see.
We use a hosted iframe for credit card authorization. So my scripts, when they get to the page, switchTo the hosted frame, fill in the credit card data, submit the data, then switch back to the defaultContent and then proceed.

driver.switchTo().frame(driver.findElementByCssSelector(<iframe selector>));
    ...<commands to fill in data>
    driver.findElementByCssSelector(<submit button selector>).click();
driver.switchTo().defaultContent();

The error output I get does not show any issues with this. It is the next click that gives me this error:
java.lang.RuntimeException: target frame detached

My guess is that driver.switchTo().defaultContent(); is failing without throwing an error so that the script thinks it's switched back but it's still on the iframe, and thus the error on the next step. While trying to figure out a work around, I took out the switch back to the defaultContainer, and I get exactly the same result, error on the click after the submit.
I'm sorry I don't have a place anyone else can use to reproduce, but I get this error every time this way with Chrome 100.0.4896.60 (browser and driver).

Hello, let me share a part of ChromeDriver log when we have encountered the issue.
Like others, we started to see the issue since 99.  We have many test cases, but it happens at only one specific part and the failure rate seems under 10%.

- It happens during switching to the top frame (same as the above comment)
- I'm not sure if it's related to the reason, but I've never seen the issue when we execute tests though Selenium server (like BrowserStack, Sauce Labs).  Reproduces only when we launch ChromeDriver directly.

We are seeing exactly the same as two last comments above.
In our case most failures are also happening after we entered credit card info in a dedicated iframe and then we switch back to default context.

However, tests don't fail always in the same point, as once we're in default context again, we need to fill 7 more input fields and our tests fail in any of them.

Regarding last comment about BrowserStack, SauceLabs, etc., for us this is reproducible since Chrome 99:
- using ChromeDriver locally
- using docker-selenium images locally and in AWS

I need a fix for this please!! Reproduced 100% in my python script.

Yes, I too need a fix for this and able to reproduce every time when I run my script in AutoBot.

BTW - I tested on latest Chrome Beta (101) and Dev (102) versions and it was still occurring there as well.

adding drive.page_source at this point in my code seems to have fixed this issue for me...I have not been able to reproduce the issue at all with this line added. Try it and let me know if it works for you all as well!

Chromedriver 101.0.4951.15 also occurs "error: target frame detached" and "error: session deleted due to page crash".

This issue is proportional to the number of subframes.
And even 99 occurs from a specific version or later.

Last version that does not occur.
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/952345/

Problems arise from here.
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/952377/

If anyone knows a workaround, please let me know.

We're also getting this since upgrading to Chrome 99

We are also getting same issue. Multiple test cases are affected .. Please share if anyone has workaround

Also facing similar issues since last Saturday (April 2nd)

error message differ from time to time, and they are random but frequent.
Keyword 'Capture Page Screenshot' could not be run on failure: Message: invalid session id
Keyword 'Capture Page Screenshot' could not be run on failure: InvalidSessionIdException: Message: invalid session id
WebDriverException: Message: unknown error: session deleted because of page crash from tab crashed
WebDriverException: Message: unknown error: session deleted because of page crash from unknown error: cannot determine loading status from tab crashed
WebDriverException: Message: target frame detached (Session info: chrome=100.0.4896.75)

My Chromedriver is now 100.0.4896.60 but I was also having the problems with 99.0.4844.84

We are facing the same issue since the chrome browser in out CI upgraded to 99.
We are seeing this issue in two pages.
1. When we are trying to access a text value. It gave error: element xyz not found, but we added code to switch to the frame before accessing it, and now it works fine. But this updated code doesn't work in Firefox/chrome v98. while the earlier code works on chrome98 and Firefox.
2. When content of the frame gets updated on click of button present inside the frame. On trying to access any element (url/button/text) we see error: target frame detached. This issue seems mainly related to handling of content refresh/reload inside the frame.

[Comment Deleted]

+1 Really desperate for a fix ASAP as my projects are being held back by these errors. Breaking all of my automation/projects.

If we don't see a fix in the upcoming release, it gonna raise a lot of questions!

This may be an OS related issue. We ran into this error running automation on a macOS Monterey 12.3.1 with Chrome v99 and v100 with related chromedrivers. The same automation runs as expected on Windows 10 Pro 19044.1586 with Chrome v99 and v100 with related chromedrivers.

I REALLY need a solution to this...please!!!!!

+1 really need to fix, due to this its causing unwanted failures in the app, and we would need to rerun the scripts to find that nothing has changed/broke on the app, this is causing major inconsistentcy in automations.

Developers,
It seems like a number of people are blocked by this issue, but we haven't see any activity. What can we ChromeDriver users do to get some movement on this? Is there something we haven't provided? Is there anything we can do to help you?
Thanks.

There is still no simple repro case. That would help chrome developers to investigate. I tried creating one with few pages and iframes, but couldn't. Maybe someone is able to simplify their failing test case so that it can be shared and it still fails?

Vladimir, could you PTAL?

We will start working on this issue later in this quarter.

Please help, I cannot use Selenium, really need to.

Here's an attempt to provide a reproduction:
Was successfully using chromedriver98.0.4758.8 to scrape rows on:
1) https://thefly.com//news.php , iterating through rows, then "loading more" at the bottom (via selenium)
2) https://finviz.com/screener.ashx?v=152&o=-shortinterestshare&c=0,1,2,3,4,5,6,7,25,30,31,65,66,67&r=1 , changing r=1, to r=2 etc

A week or two ago, upgraded to chromedriver100.0.4896.60 which caused Chrome to crash (wasnt target frame detached error, but was something about session not found etc - I tried to debug, but could never find the source of the exception, just the same exception/message no matter what I asked of the driver)
Today, upgraded to chromedriver101.0.4951.41, which caused Chrome to crash with the target frame detached error; Was hoping this upgrade would fix it, instead seems to crash pretty quickly still (only tested this latest version with site #1 above) and with a new error

On site #1 above, the crash is usually almost immediate
On site #2 above, the crash isnt nearly as consistent - it could be 20, 30, 40 pages

Here are my Python selenium arguments -- note that headless or with a head, doesnt seem to matter:
        options.add_argument('--no-sandbox')
        options.add_argument("--disable-extensions")
        options.add_argument("--disable-notifications")
        options.add_argument("--disable-gpu")
        options.add_argument("--disable-blink-features")
        options.add_argument('--disable-blink-features=AutomationControlled')
        options.add_argument('--disable-dev-shm-usage')
       
        if headless == True:
            options.add_argument('--headless')

I've tried different user agents, since that in the past had given me problems with other issues.  Doesnt seem to matter:
        user_agent = 'Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.2 (KHTML, like Gecko) Chrome/22.0.1216.0 Safari/537.2'
        user_agent = "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36" -- this is my actual user agent as per google ("what is my user agent")

I also upgraded Selenium last week to the latest. I had been using 3.x but upgraded to 4 in an attempt to resolve this. Didnt seem to matter.

It seems to crash not on one particular call to the driver, but pretty randomly - some specific state of the website, rather than a specific call to the driver.  Ive used chromedriver100.0.4896.60 on another website with no problems (upgraded to 101 today, so I dont know if that now crashes). Site #1 (especially) and site #2 have pop-up ads / are pretty busy websites - lots of iframes I suspect, whereas the other site with no problem was more simple, no ads and popups etc.

Now for the stacktrace(s):

It has crashed before (with version 100) on driver.get( <ENTER SITE #1 URL > ), among other calls, but right now, it just crashed with this stack trace:

    self.driver.find_elements(by=By.XPATH, value="//*[@id='search_news']/div[@class='newsFeedWidget feedCerrado']/table/tbody/tr" + dataTopicXPath)
    Python\Python39\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 1283, in find_elements
    return self.execute(Command.FIND_ELEMENTS, {
  Python\Python39\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 425, in execute
    self.error_handler.check_response(response)
  Python\Python39\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 247, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: target frame detached
  (Session info: chrome=101.0.4951.41)
Stacktrace:
(no stacktrace)
I do have a backtrace if that would be helpful.


Hope that helps.  Happy provide more if I can.

After thinking about this some more, I thought it would be much more helpful if I developed an encapsulated/portable program that you should be able to use to reproduce my error.

I've run this genericized version of my program a handful of times and it has crashed (within a few minutes of starting it) about half the time. This time around, I am receiving slightly different error messages, which seem to correspond to a different call to the driver than the one that I pointed to a few hours ago in my last post.

I've attached the full program so that you can reproduce.  Python 3.9, Selenium 4 (downloaded very recently), Windows 10, Chrome Version 101.0.4951.41 (Official Build) (64-bit), Chromium 101.0.4951.41.  But it also crashed earliest this week and last week with Selenium 3.x and Chrome 100.0.4896.127 and Chromium 100.0.4896.60 and those same Chrome/Chromium versions with Selenium 4.

In the attached program, there are lots of sleep.time calls, which were another of my attempts to solve this issue. They can probably be removed or the time reduced.  They do not seem to be having an effect - or not enough of an effect. I also had googled my prior errors which someone indicated might be due to running this in a multi-threaded program, but the attached program is single threaded, so that's probably not it.

triggerElement = self.getOneByXpath("//*[@id='search_news']/div[@class='moreNewsTriggers']")
    result = self.driver.find_element(by=By.XPATH, value=path)
    return self.execute(Command.FIND_ELEMENT, {
    self.error_handler.check_response(response)
    raise exception_class(message, screen, stacktrace)
from unknown error: cannot determine loading status
from tab crashed
  (Session info: chrome=101.0.4951.41)
Stacktrace:
Backtrace: (it has a long backtrace)

Chrome just crashed again from running the program again, producing this error (running the same program but with headless=True).  Guessing all of these crashes have the same root cause, but result in different error messages depending on which part of the code runs into the root problem.

    self.scrollDown()
    self.driver.execute_script("arguments[0].scrollIntoView();", triggerElement)
    return self.execute(command, {
    self.error_handler.check_response(response)
    raise exception_class(message, screen, stacktrace)
  (Session info: headless chrome=101.0.4951.41)
Stacktrace:
Backtrace:

[Empty comment from Monorail migration]

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src/+/481b75fc3dc00cedaa3f09403ffd67c29f080447

commit 481b75fc3dc00cedaa3f09403ffd67c29f080447
Author: Vladimir Nechaev <nechaev@chromium.org>
Date: Tue May 10 15:16:58 2022

Get rid of DomTracker

NodeId's can be invalidated between remote calls.
Use of NodeId's can lead to errors with unresolved nodes.

Bug: chromedriver:4048
Change-Id: I6d60587a2f6da97bf5b71c440bca2396625296f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3634385
Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Vladimir Nechaev <nechaev@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1001507}

[modify] https://crrev.com/481b75fc3dc00cedaa3f09403ffd67c29f080447/chrome/test/chromedriver/chrome/web_view.h
[modify] https://crrev.com/481b75fc3dc00cedaa3f09403ffd67c29f080447/chrome/test/chromedriver/BUILD.gn
[modify] https://crrev.com/481b75fc3dc00cedaa3f09403ffd67c29f080447/chrome/test/chromedriver/chrome/web_view_impl.cc
[modify] https://crrev.com/481b75fc3dc00cedaa3f09403ffd67c29f080447/chrome/test/chromedriver/element_util.cc
[delete] https://crrev.com/8805f4d057b3287615bf58f7c494aa03886a56ff/chrome/test/chromedriver/chrome/dom_tracker.cc
[delete] https://crrev.com/8805f4d057b3287615bf58f7c494aa03886a56ff/chrome/test/chromedriver/chrome/dom_tracker_unittest.cc
[delete] https://crrev.com/8805f4d057b3287615bf58f7c494aa03886a56ff/chrome/test/chromedriver/chrome/dom_tracker.h
[modify] https://crrev.com/481b75fc3dc00cedaa3f09403ffd67c29f080447/chrome/test/chromedriver/chrome/web_view_impl.h
[modify] https://crrev.com/481b75fc3dc00cedaa3f09403ffd67c29f080447/chrome/test/chromedriver/chrome/stub_web_view.cc
[modify] https://crrev.com/481b75fc3dc00cedaa3f09403ffd67c29f080447/chrome/test/chromedriver/chrome/stub_web_view.h

We could not reproduce the bug but found 2 issues in the code that have been addressed.
Their fix was submitted yesterday and is avaialble in today's canary:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/1001938/

I installed the version linked to, but I had to find the Windows version of that release. Then I discovered it only works with Chrome 103, which is not released, so I had to figure out how to get that. Once I did though, I ran my tests that had failed with this, and they are now working. So thank you team!
Unfortunately, the browser change has reverted somehow in some of the VMs, so I need to determine why that happened.
Link for windows version of chromedriver and chrome 103:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/1002137/

org.openqa.selenium.WebDriverException: target frame detached
  (Session info: chrome=101.0.4951.64)

- This issue still happens in the version 101 also.

mpage@eline.com ChromeDriver 103 works with Chrome 102 (beta).
The other canary builds are available here:https://chromedriver.chromium.org/chromedriver-canary

I am still getting a lot of errors using Version 102.0.5005.115 (Build officiel) (arm64) with ChromeDriver 102.0.5005.61

invalid session id
InvalidSessionIdException
Timed out receiving message from renderer: 299.625
session deleted because of page crash from tab crashed
session deleted because of page crash from unknown error
target frame detached


see:
https://groups.google.com/g/chromedriver-users/c/QjGnZ_gLgVI/m/srWXS8YhAQAJ
https://groups.google.com/g/chromedriver-users/c/Z_CaHJTJnLw/m/QawoSbC9AwAJ

Dear  dflageole@lapresse.ca!
The bug is fixed in ChromeDriver 103 Beta.

 Though target frame detached error is now not observed but we are now seeing another issue with 103 beta WebDriverException unknown error: unexpected command response.

here is a snippet from the webdriver logs (also attached)
DevTools WebSocket Response:  (id=1) 07531346254D69AE0EA02B16CA7D80C9 {"code":-32001,"message":"Session with given id not found."}
[1655718826.569][INFO]: Waiting for pending navigations...
[1655718826.569][DEBUG]: DevTools WebSocket Response:  (id=2) 07531346254D69AE0EA02B16CA7D80C9 {"code":-32001,"message":"Session with given id not found."}
[1655718826.569][INFO]: Done waiting for pending navigations. Status: unknown error: unexpected command response
[1655718826.569][INFO]: [9eb595e29128297058a7f53961e18487] RESPONSE Navigate ERROR unknown error: unexpected command response

We have raised another issue here for this but need to see if this is related to the fix for target frame detached.
https://bugs.chromium.org/p/chromedriver/issues/detail?id=4135
https://bugs.chromium.org/p/chromium/issues/detail?id=1337748

Frame detached issue is fixed in ChromeDriver 103

[Empty comment from Monorail migration]

[Empty comment from Monorail migration]

[Empty comment from Monorail migration]

Is this issue fixed in ChromeDriver v103? Am able to replicate the same error with Chrome 103 Beta. Is this fixed in the stable release? Is there an ETA to fix it if not? Thanks!

here is a snippet of my selenium logs showing this error:
"value":{"error":"unknown error","message":"unknown error: cannot determine loading status\nfrom unknown error: cannot determine loading status\nfrom unknown error: unexpected command response\n  (Session info: chrome=103.0.5060.24)

this issue is not fixed in chrome 103, please reopen

Dear dalimian@gmail.com,
Do you observe the "Target frame detached" error or "loading status" error or something else?

@nechaev@chromium.org

here is an example

Appium error: An unknown server-side error occurred while processing the command. Original error: unknown error: cannot determine loading status
from unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)
  (Driver info: chromedriver=103.0.5060.53 (a1711811edd74ff1cf2150f36ffa3b0dae40b17f-refs/branch-heads/5060@{#853}),platform=Linux 4.1.13-101.fc21.x86_64 x86_64)
[

android 11
appium 1.17.0

Thank you dalimian.
Your example does not contain the "frame detached" message.
As for "unexpected command response" the issue was fixed in 103.0.5060.134.
Please updated your ChromeDriver

I can repro the "frame detached" error in Chrome 105. In my case there are two iframes that are nested in a popup window. Clicking a Submit button inside the nested iframe closes the window containing the iframes. The exception occurs immediately after I click the Submit button.

This issue was migrated from crbug.com/chromedriver/4048?no_tracker_redirect=1

[Monorail mergedwith: crbug.com/chromedriver/4053, crbug.com/chromedriver/4090]
[Monorail components added to Component Tags custom field.]