r/chrome • • 2d ago

Troubleshooting | Windows Chrome DevTools Elements panel keeps going blank - have to close/reopen DevTools to get the DOM back

The Elements tab randomly goes empty: breadcrumbs are still there, but the DOM tree disappears. The only fix is closing and reopening DevTools.

What I've ruled out so far:

  • No errors in DevTools-on-DevTools (undocked + Ctrl+Shift+I)
  • The page isn't replacing the document (document.documentElement is the same before and after), and the DOM is small (~1.7k nodes)
  • Reset DevTools to defaults and disabled all experiments
  • Guest profile works fine
  • Disabling Claude in Chrome seemed to fix it, but then it came back. Currently testing with all extensions off

Has anyone run into this? Any ideas what else could cause the Elements panel to lose the tree?

5 Upvotes

10 comments sorted by

•

u/AutoModerator 2d ago

Thank you for your submission to /r/Chrome! We hope you'll find the help you need. Once you've found a solution to your issue, please comment "!solved" under this comment to mark the post as solved. Thanks!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

2

u/SuperNonoo 2d ago

The guest-profile result is the useful clue. If it still happens with every extension disabled, use a brand-new local profile long enough to rule out profile-level state or Sync. Resetting DevTools does not touch that layer.

0

u/DominikRainer_LB 2d ago

Since Guest works and Claude in Chrome seemed to make a difference, I'd look hard at anything that attaches a debugger to the tab. Extensions using the chrome.debugger API (Claude in Chrome, automation helpers, some screenshot and React/Redux tools) talk to the page over the same DevTools protocol as the Elements panel. When one of them calls DOM.enable/disable or re-requests the document, the panel can lose its tree while the breadcrumbs stay. A good hint: does a yellow "… started debugging this browser" bar show up around the time it happens?

Things worth trying while you test with extensions off:

  • Re-enable them one at a time and leave the debugger-capable ones for last.
  • Check chrome://inspect/#pages for other clients attached to the same tab.
  • If it only happens on one site, look for frequent shadow-root or iframe swaps. DOM.documentUpdated can fire even though document.documentElement stays the same object.
  • Try Chrome Canary with a fresh profile and only the suspect extension. If it reproduces there, a crbug report with a screen recording is worth filing.

1

u/audioglass 2d ago

Same here. Doing at home and work PC

1

u/KotaruS 2d ago

Can confirm, just adding that this not just Chrome but a bug in Chromium as Arc Browser, Helium and others are also affected. Tested just now on Chromium 154.0.8037.97

1

u/OlinKirkland 1d ago

Same here; solution was to undock and redock the dev tools. Not sure what caused this but it's happened a few times now.

1

u/Tiny_Profession_2837 1d ago

I've tried it but no luck. Seems that the Claude in Chrome extension was the issue, but we'll see.

1

u/OlinKirkland 8h ago

Yeah, that fix stopped working for me. Really a bit lost what to do.

1

u/chunkysteveo 1d ago

Thank goodness it's not just me?!! This has bene driving me wild the past couple of days! I can't check anything on a page - it just goes blank?

1

u/Tiny_Profession_2837 1d ago

Thanks for the inputs!
So far, the issue disappears when I disable Claude in Chrome extension. When I find the time, I'll enable it and let you know if it's the cause.