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

[joshkaplan]

Website or app

https://getstream.github.io/website-react-examples/team/?user=autumn-salad-3&user_token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiYXV0dW1uLXNhbGFkLTMiLCJleHAiOjE2MjQ2Nzc2MDl9.RgvfWl8k9lsuXIlQ4cM0eCJ6NU8aa1oPiYRe0Pa6zsY&target_origin=https://getstream.io

Repro steps

1. Go to this GetStream.io demo app
2. Open React dev tools
3. Send a message in the app
4. Error

How often does this bug happen?

Every time

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.13.5-0ae5290b54

Error message (automated)

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

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:21178:43
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19286:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19446:12
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:37413:39)

Error component stack (automated)

No response

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

[bvaughn]

Neat app!

I can't reproduce the bug at the URL following the steps you provided, though.

[Daniel15]

I sometimes hit this issue internally at Facebook too. I can repro in Chrome but not in Firefox.

[Daniel15]

@bvaughn I posted in the Workplace group with a repro :) -- Regards, Daniel Lo Nigro https://d.sb[https://d.sb/]

…

Sent from my phone Jul 14, 2021 8:54:43 AM Brian Vaughn ***@***.***>:

@Daniel15[https://github.com/Daniel15] Sharing repro steps with me would be helpful. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub[#21755 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAWOHLR6YTBDTL2R64TRALTXWXMDANCNFSM47KVCR5A]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD8AAAA/CAYAAABXXxDfAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAmSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAJwY+QwABivJx1AAAAABJRU5ErkJggg==###24x24:true###][Tracking image][https://github.com/notifications/beacon/AAAWOHOKHAXSIYREXCMKV4LTXWXMDA5CNFSM47KVCR5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGRZ6MJA.gif]

[sfleiter]

Any news?
This is happening quite often in main thread overload scenrios for me.

[bvaughn]

If you're able to repro this, @sfleiter, you might be in a good place to potential investigate and share ideas for a fix. In case it's not clear from the thread above, I have not been able to reproduce it myself.

[ShivamS136]

This and the other bug #21755 seem related as I started to face both together.

[afreen23]

I hit this today in firefox.
Something like Cannot remove node "6809" because no matching node was found in the Store.

[bvaughn]

Hey folks 👋🏼

Leaving "me too" comments isn't very helpful. What we need is a way to reproduce this bug on our end so we can (a) see what's causing it and (b) implement and confirm a fix.

If you can share a way to reliably reproduce this with us please do.

[Mayank-MP05]

I too faced the Same Bug while working with react-dev-tools but when I clicked reinstalled dev tools its temporarily vanished

[Edgarmejiav]

I changed from Chrome to Edge and I no longer had the error, it is very rare to be honest

[eps1lon]

@bvaughn Repro using react@18.0.0-alpha-996da67b2-20211018. I tried to reduce the components used as much as possible. Seems to just crash once a certain number of nodes stored is reached. Can try to reduce it further if the repro is insufficient.

Website or app

http://localhost:3000/components/transfer-list/ from https://github.com/eps1lon/material-ui/tree/df6b296d52bc58ee908ef1d4c27e14030d28b347

Repro steps

1. git clone https://github.com/eps1lon/material-ui.git
2. git checkout df6b296d52bc58ee908ef1d4c27e14030d28b347
3. yarn
4. yarn docs:dev
5. Goto http://localhost:3000/components/text-fields/
6. Open Profiler
7. Click "Reload and start profiling"

How often does this bug happen?

Non deterministic.

DevTools package (automated)

e5f486b

DevTools version (automated)

4.20.0-e5f486b5a

Error message (automated)

Uncaught Error: Cannot remove node "177" because no matching node was found in the Store.

Error call stack (automated)

The error was thrown at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25851:43
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:23957:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24117:12
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:52741:41)

Error component stack (automated)

No response

GitHub query string (automated)

No response

[Liquid2Sky]

After updating Flipper to Version 127 (coming from 125) I got that error while debugging a react-native app too.
However it seems that only build in version of devtools (4.22.1) is affected, switching to global installed version (4.11.0) everything works fine.

I am on an Apple M1 MBP and that was often the cause of problems related to react / react-native development 🙃
@eps1lon @joshkaplan Are you on an M1 too?