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

Error: "Could not find node with id "57" in commit tree" #17749

Closed
ngoxuanhien opened this issue Dec 31, 2019 · 2 comments
Closed

Error: "Could not find node with id "57" in commit tree" #17749

ngoxuanhien opened this issue Dec 31, 2019 · 2 comments

Comments

@ngoxuanhien
Copy link

I'm tried to use *Profilter tool on Chrome browser, but i got this error when i review the rank of list Elements. I don't know what is that ?

DevTools version: 4.2.1-3816ae7c3

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157108
at Map.forEach ()
at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157054)
at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157577)
at vl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:314907)
at gi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59907)
at jl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:107381)
at Lc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92715)
at Pc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92640)
at wc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89544)

Component stack: in vl
in div
in div
in div
in wo
in Unknown
in n
in Unknown
in div
in div
in Li
in $e
in dn
in Ca
in Pc

@bvaughn
Copy link
Contributor

bvaughn commented Dec 31, 2019

Sorry for the inconvenience here. This is a known issue (#16446) but I don't yet know the underlying cause or fix.

I'm going to close this as a duplicate. If you'd be interested in lending a hand on #16446, I'd welcome the help. Otherwise I'll hopefully fix it eventually 😄

@ngoxuanhien
Copy link
Author

Sorry for the inconvenience here. This is a known issue (#16446) but I don't yet know the underlying cause or fix.

I'm going to close this as a duplicate. If you'd be interested in lending a hand on #16446, I'd welcome the help. Otherwise I'll hopefully fix it eventually 😄

ok thank you :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants