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 "2153" in commit tree" #17872

Closed
cristinamarin22 opened this issue Jan 20, 2020 · 3 comments
Closed

Error: "Could not find node with id "2153" in commit tree" #17872

cristinamarin22 opened this issue Jan 20, 2020 · 3 comments

Comments

@cristinamarin22
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.4.0-f749045a5

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:159909
at Map.forEach ()
at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:159855)
at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:160378)
at Sl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:323092)
at ei (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:58864)
at yl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:106932)
at kc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:99474)
at wc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:99399)
at fc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:96173)

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

@ecreeth
Copy link

ecreeth commented Jan 20, 2020

#17802 (comment)

@bvaughn
Copy link
Contributor

bvaughn commented Jan 20, 2020

4.4.0-f749045a5 should have the fix mentioned in that comment. So it seems like this bug is still around, just firing less frequently.

@cristinamarin22 Can you fill in the details on this part of the issue template?

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

@bvaughn
Copy link
Contributor

bvaughn commented Mar 25, 2020

I landed PR #18378 this morning. It fixes a source of problem that I think might be responsible for this, and some of the other infrequent Profiler errors. I'll release an update to the Chrome/Firefox/Edge stores today.

@bvaughn bvaughn closed this as completed Mar 25, 2020
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