Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
iburlachenko opened this issue Dec 3, 2021 · 1 comment
Labels

Comments

@iburlachenko
Copy link

iburlachenko commented Dec 3, 2021

Website or app

https://pasteboard.co/6Ec3lSzDE4Yz.png

Repro steps

  1. Open Chrome with 50+ tabs.
  2. Run React-based website locally.
  3. Open Chrome Dev Tools to investigate ActiveLink component hierarchy inside Navbar component.
  4. ActiveLink component from Next was used.
  5. Get uncaught error Screenshot

How often does this bug happen?

Sometimes

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.21.0-2f8f60ca8

Error message (automated)

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

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26134:41
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24349:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24509:12
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:53230: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
@iburlachenko iburlachenko added Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug labels Dec 3, 2021
@bvaughn
Copy link
Contributor

bvaughn commented Dec 4, 2021

I'm sorry you experienced this bug! 🙇

Looks like this problem was already reported though (#21636) so I'm going to mark this issue as a duplicate and close it. If you have additional context that might help us repro this problem, please leave a comment on the other issue!

Thank you~

@bvaughn bvaughn closed this as completed Dec 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants