-
Notifications
You must be signed in to change notification settings - Fork 47k
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: "Cannot read property 'duration' of undefined" #18798
Comments
Looks like duplicate of #18786 🤔 |
Here is a deployed repro case: https://react-example1.s3.amazonaws.com/index.html Steps:
You can find the code for the case here: https://github.com/shiftyp/object-hooks/blob/experimental-tracing/packages/object-hooks/src/useInstances.ts#L37 |
Thanks for the repro case, @shiftyp! |
@shiftyp Did you forget to commit something? Checking out the
Seems like a problem with the workspace configuration or something?
I was able to run |
We used to filter "empty" DevTools commits, but it was error prone (see facebook#18798). A commit may appear to be empty (no actual durations) because of component filters, but filtering these empty commits causes interaction commit indices to be off by N. This not only corrupts the resulting data, but also potentially causes runtime errors. For that matter, hiding "empty" commits might cause confusion too. A commit *did happen* even if none of the components the Profiler is showing were involved.
Disregard. The remote repro was sufficient. Thanks for sharing it! |
* Disable Profiler commit filtering We used to filter "empty" DevTools commits, but it was error prone (see #18798). A commit may appear to be empty (no actual durations) because of component filters, but filtering these empty commits causes interaction commit indices to be off by N. This not only corrupts the resulting data, but also potentially causes runtime errors. For that matter, hiding "empty" commits might cause confusion too. A commit *did happen* even if none of the components the Profiler is showing were involved. * Restart flaky CI
Describe what you were doing when the bug occurred:
Please do not remove the text below this line
DevTools version: 4.6.0-6cceaeb67
Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:344360
at Array.map ()
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:344166
at ci (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59620)
at Ll (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:109960)
at qc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:102381)
at Hc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:102306)
at Vc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:102171)
at Tc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:98781)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:46014
Component stack: in Unknown
in Unknown
in div
in div
in n
in div
in bc
in div
in n
in div
in vc
in div
in div
in div
in So
in Unknown
in n
in Unknown
in div
in div
in rl
in Ze
in fn
in Ga
in _s
The text was updated successfully, but these errors were encountered: