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 "32" in commit tree" #17823

Closed
amitbaral opened this issue Jan 12, 2020 · 2 comments
Closed

Error: "Could not find node with id "32" in commit tree" #17823

amitbaral opened this issue Jan 12, 2020 · 2 comments

Comments

@amitbaral
Copy link

Describe what you were doing when the bug occurred:
1.
2.
3.


Please do not remove the text below this line

DevTools version: 4.3.0-3e0967783

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:159833
at Map.forEach ()
at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:159779)
at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:160302)
at Sl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:322998)
at ii (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59363)
at Sl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:107431)
at Ic (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:99973)
at Tc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:99898)
at vc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:96672)

Component stack: in Sl
in div
in div
in div
in vo
in Unknown
in n
in Unknown
in div
in div
in Qi
in Ve
in nn
in Da
in Yc

@necolas
Copy link
Contributor

necolas commented Jan 12, 2020

This is not an actionable issue report and does not provide the details we request in the issue template, so it is being closed

@necolas necolas closed this as completed Jan 12, 2020
@bvaughn
Copy link
Contributor

bvaughn commented Jan 12, 2020

This looks like a duplicate of #16446, hopefully fixed via #17771. The fix rolled out to the Chrome store this week but it seems like it hasn't yet been installed on your browser. Try restarting Chrome to see if that pulls in the latest version (v4.4) and hopefully that will fix things for you.

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

3 participants