You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[DevTools Bug] Cannot remove node "226752" because no matching node was found in the Store. #26793
Cannot remove node "226752" because no matching node was found in the Store.
Error call stack (automated)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28710:43
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 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
Also came across this issue and had to remove the 4.27.6 version and then added 4.27.7 version, the latest. This seems to have fixed the related issues at least in chrome.
I'm seeing this in 4.27.7. It seems to get triggered every time I wrap a component in React.memo(). To clear the error I have to kill my webpack dev server and restart Chrome.
I did some profiling in react dev tools with 4.27.8 today, and did not have any issues.
I wouldn't take this as 100% confirmation that the issue is fixed though, since I wasn't able to reproduce the issue consistently before (my previous comment was premature/wrong).
I did some profiling in react dev tools with 4.27.8 today, and did not have any issues.
I wouldn't take this as 100% confirmation that the issue is fixed though, since I wasn't able to reproduce the issue consistently before (my previous comment was premature/wrong).
Sure, thanks for checking.
Currently working on stabilizing the extension behaviour. Keeping this issue open, as this problem is hardly reproducible, would be nice if someone can come up with a reproducible example.
Activity
YardWill commentedon May 8, 2023
Same to me. Both in Edge Version 4.27.7 (5/7/2023) and Chrome 4.27.6 (4/20/2023)
YardWill commentedon May 9, 2023
It seems that the issue was caused by this PR(#26615). I reverted the version back to 4.27.5 and it worked.
pitter2416 commentedon May 9, 2023
I also encountered the same problem, did you solve it? https://www.ectcm.com
YardWill commentedon May 9, 2023
revert extensions version to 4.27.5
jrbartola commentedon May 9, 2023
Also seeing this problem- the extension is unusable now. Reverting it seems like more effort than it's worth :/
haniffaraz commentedon May 10, 2023
Also came across this issue and had to remove the
4.27.6version and then added4.27.7version, the latest. This seems to have fixed the related issues at least in chrome.literalpie commentedon May 11, 2023
I'm seeing this in 4.27.7. It seems to get triggered every time I wrap a component in
React.memo(). To clear the error I have to kill my webpack dev server and restart Chrome.React DevTools 4.27.7 -> 4.27.8 (#26823)
hoxyq commentedon May 22, 2023
Hey, can anyone try to reproduce this with version 4.27.8 installed?
literalpie commentedon May 22, 2023
I did some profiling in react dev tools with 4.27.8 today, and did not have any issues.
I wouldn't take this as 100% confirmation that the issue is fixed though, since I wasn't able to reproduce the issue consistently before (my previous comment was premature/wrong).
hoxyq commentedon May 22, 2023
Sure, thanks for checking.
Currently working on stabilizing the extension behaviour. Keeping this issue open, as this problem is hardly reproducible, would be nice if someone can come up with a reproducible example.
uaeio commentedon May 24, 2023
I have such error when reloading page during profile:
Suvikr23 commentedon Jun 7, 2023
Faced this exact same error while profiling:
Uncaught Error: Cannot remove node "3755" because no matching node was found in the Store.fix[devtools/updateFiberRecursively]: mount suspense fallback set in …
React DevTools 4.27.7 -> 4.27.8 (react#26823)
fix[devtools/updateFiberRecursively]: mount suspense fallback set in …
React DevTools 4.27.7 -> 4.27.8 (#26823)
fix[devtools/updateFiberRecursively]: mount suspense fallback set in …