[DevTools Bug]: Blank tools localhost - react_devtools_backend.js:5821 Uncaught Error: Could not find ID for Fiber

[CatarinaSony]

Website or app

www.google.com

Repro steps

React Devtools - 4.20.0
React - 16.8.6

Not sure if relevant but:
react-scripts 4.0.3

First I get an blank devtools (components) but when picking select element arrow and hover over elements a lot of errors like this one shows up in the console:

react_devtools_backend.js:5821 Uncaught Error: Could not find ID for Fiber "Context.Provider"
    at getFiberIDThrows (react_devtools_backend.js:5821)
    at Object.getFiberIDForNative (react_devtools_backend.js:7257)
    at Overlay_Overlay.inspect (react_devtools_backend.js:9158)
    at showOverlay (react_devtools_backend.js:9286)
    at onPointerOver (react_devtools_backend.js:9445)
getFiberIDThrows @ react_devtools_backend.js:5821
getFiberIDForNative @ react_devtools_backend.js:7257
inspect @ react_devtools_backend.js:9158
showOverlay @ react_devtools_backend.js:9286
onPointerOver @ react_devtools_backend.js:9445

No other errors occur. Devtools works fine on deployed version. Eg. https://reactjs.org/ works fine.

PR and issue that could be related?
Issue 22577
PR 22527

Maybe relevant comment from author and maintainer of React DevTools:
Earlier fiber problem

How often does this bug happen?

Every time

DevTools package (automated)

No response

DevTools version (automated)

No response

Error message (automated)

No response

Error call stack (automated)

No response

Error component stack (automated)

No response

GitHub query string (automated)

No response

[github-actions]

@CatarinaSony: We're sorry you've seen this error. ❤️

Unfortunately the URL you provided ("localhost") is not publicly accessible. (This means that we will not be able to reproduce the problem you're reporting.)

Please help us by providing a link to a CodeSandbox (https://codesandbox.io/s/new), a repository on GitHub, or a minimal code example that reproduces the problem. (Screenshots or videos can also be helpful if they help provide context on how to repro the bug.)

Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

Issues without repros are automatically closed but we will re-open if you update with repro info.

[github-actions]

Thank you for providing repro steps! Re-opening issue now for triage.

[jstejada]

It seems like this might be a duplicate of #22577, so I'm merging into that one