[DevTools Bug] Cannot remove node "25" because no matching node was found in the Store.

[vinaymarati]

Website or app

https://vinaykumardku2zrjsivsfcbc.drops.nxtwave.tech/

Repro steps

.

How often does this bug happen?

Every time

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

6.1.2-4d6cf75921

Error message (automated)

Cannot remove node "25" because no matching node was found in the Store.

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1228673
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1195122)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1196729
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1607819)

Error component stack (automated)

GitHub query string (automated)

https://api.github.com/search/issues?q=Cannot remove node  because no matching node was found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react

[zhg163]

Thank you for reporting this issue. Could you please provide more information about your React and React DevTools versions? This would help in investigating the problem.

[skylarmb]

I am seeing this intermittently as well.

• Firefox 138.0.4
• React 19.1.0
• React Developer Tools 6.0.0

Seems to happen if I have react devtools open when I load / reload the page. If I open them after loading the page it seems to work?

[janvorwerk]

Seems very much related to #32852 I get these errors all the time => the profiler is pretty much unusable 😢

[Hardanish-Singh]

Looks like its related to #32852

[AstralHunt]

These "Cannot Remove node ... found in Store" issues are prevalent...

[Ahmard]

I am seeing this intermittently as well.

* Firefox 138.0.4

* React 19.1.0

* React Developer Tools 6.0.0

Seems to happen if I have react devtools open when I load / reload the page. If I open them after loading the page it seems to work?

Having same behavior here as well, it only happens when you open the devtool and reload the page.