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

[aluiscode]

Website or app

https://soshace.com/react-user-login-authentication-using-usecontext-and-usereducer/

Repro steps

I'm using a context to manage app global state like in Website when get that error

How often does this bug happen?

Every time

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.13.2-e468072e17

Error message (automated)

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

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:21477:43
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19585:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19745:12
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:37733: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]

@lazcanocode Can you tell me exactly what you need to on a website in order to cause the bug to happen? The website you linked doesn't even use React. Looks like it's a tutorial on how to build a website. I've used the Code Sandbox linked to at the end of the tutorial though and I don't see an error.

[nikglavin]

Here's a stack that I got when encountering the same error, the error occurs when I turn on the Record why each component rendered while profiling setting, after turning it off the profiler started to work again

Currently my steps to reproduce are

• Refresh the page
• Enable Record why each component rendered while profiling
• Start profiler and perform interaction
• 💣

Note
The following doesn't cause an error

• Refresh page
• Disable Record why each component rendered
• Start profiler and perform interaction
• Stop profiler
• Enable Record why each component rendered
• Start profile and perform interaction
• Stop profile
• View the flame graph

Uncaught Error: Cannot remove node "1262" because no matching node was found in the Store.
The error was thrown at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:21477:43
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19585:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19745:12
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:37733:39)

index.js:1 Warning: React instrumentation encountered an error: TypeError: memoizedState.hasOwnProperty is not a function
console.<computed> @ index.js:1
overrideMethod @ react_devtools_backend.js:2557
printWarning @ react-dom.development.js:67
error @ react-dom.development.js:43
onCommitRoot @ react-dom.development.js:11146
commitRootImpl @ react-dom.development.js:23261
unstable_runWithPriority @ scheduler.development.js:646
runWithPriority$1 @ react-dom.development.js:11276
commitRoot @ react-dom.development.js:22990
performSyncWorkOnRoot @ react-dom.development.js:22329
(anonymous) @ react-dom.development.js:11327
unstable_runWithPriority @ scheduler.development.js:646
runWithPriority$1 @ react-dom.development.js:11276
flushSyncCallbackQueueImpl @ react-dom.development.js:11322
flushSyncCallbackQueue @ react-dom.development.js:11309
discreteUpdates$1 @ react-dom.development.js:22420
discreteUpdates @ react-dom.development.js:3756
dispatchDiscreteEvent @ react-dom.development.js:5889

VM127 react_devtools_backend.js:5825 Uncaught TypeError: memoizedState.hasOwnProperty is not a function
    at isEffect (VM127 react_devtools_backend.js:5825)
    at didHookChange (VM127 react_devtools_backend.js:5832)
    at didHooksChange (VM127 react_devtools_backend.js:5847)
    at getChangeDescription (VM127 react_devtools_backend.js:5705)
    at recordProfilingDurations (VM127 react_devtools_backend.js:6435)
    at recordMount (VM127 react_devtools_backend.js:6220)
    at mountFiberRecursively (VM127 react_devtools_backend.js:6297)
    ... +10 of the above

[bvaughn]

@nikglavin Call stack isn't really helpful. A repro case is what's needed for this bug.

That being said, this is interesting:

Uncaught TypeError: memoizedState.hasOwnProperty is not a function

Are you setting a property named hasOwnProperty in your state?

This is something I can add a fix for.

[bvaughn]

I think this issue might be fixed by #21523.

If you'd like to verify, download this build:
ReactDevTools.zip

And follow these steps to install it:
https://user-images.githubusercontent.com/29597/118749019-b6cda600-b82a-11eb-9449-ef56f41eced5.mp4

Going to close for now since I don't have a solid repro. We can re-open if the above fix isn't sufficient though!

[aluiscode]

Thank you, the new version fix my problem!!!

[bvaughn]

That's great! Thanks