[DevTools Bug] Cannot add node "1751" because a node with that id is already in the Store.

[regosen]

Website or app

local repo

Repro steps

Loading a React component with the React profiler recording enabled

How often does this bug happen?

Every time

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.27.6-7f8c501f6

Error message (automated)

Cannot add node "1751" because a node with that id is already in the Store.

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28581:41
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26606:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26775:14
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:57029:39)

Error component stack (automated)

No response

GitHub query string (automated)

https://api.github.com/search/issues?q=Cannot add node  because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react

[sandip2224]

Same issue here.

Devtools version: 4.27.6 (4/20/2023)

[joepetrillo]

Same issue here. Using NextJS 13.4.1

[FlyOrDie]

Same issue here. Happens, when adding @react-three/fiber Canvas element. @react-three/fiber version 8.13.0

[apenab]

Same issue:

[IvanYulin]

same...
do you all have code for a chrome extension?

[karin-on]

same with devtools version: 4.27.7 (5/7/2023)

I've installed a React profiler via Chrome web store (https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi) which created a second copy of an extension under "From other sources" title in extensions panel, after that I've deleted a copy of an react dev tools that was 'native' to edge, and voila, profiler works.

[hoxyq]

Hey folks, the only reproducible example I've found is mentioned in #26797.

I've merged a fix for it, but need more input from you:

1. If you are constantly facing this issue, can you post here a repro please?
2. Can you please follow these instructions and try to reproduce this error again?

[brettgoss]

@hoxyq I am no longer seeing this error after installing the release you linked in #26797 (Created from revision 67a05d03e on 5/12/2023).

[hoxyq]

@hoxyq I am no longer seeing this error after installing the release you linked in #26797 (Created from revision 67a05d03e on 5/12/2023).

Great, thank you! This fix will be included in v4.27.8 release, which I will publish this week.