Devtools Profile tab seems not to show call stacks sometimes.
Reported by
trusktr@gmail.com,
Jan 2 2018
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 9901.77.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.97 Safari/537.36 Platform: 9901.77.0 (Official Build) stable-channel caroline Steps to reproduce the problem: 1. I'm not sure how to reproduce specifically. 2. I am running a requestAnimationFrame loop, and sometimes the call stack is empty (see screenshots). 3. Try recording this codepen and you may see empty frame stacks: https://s.codepen.io/trusktr/debug/rpaQqK What is the expected behavior? I would expect to see all call stacks for every frame. What went wrong? Sometimes call stacks don't appear in the timeline. Did this work before? N/A Chrome version: 62.0.3202.97 Channel: stable OS Version: 9901.77.0 Flash Version: One screenshot shows a completely empty frame, which shouldn't actually be the case because my code is like this: ``` requestAnimationFrame(function loop() { // ... do stuff ... requestAnimationFrame(loop) }) ``` so based on a render loop like that we should never see a frame with no call stack. The other screenshot shows that half the frame's callstack is missing, which shouldn't happen because the function call that I see should only happen if the stuff in the first half triggers it, so if there's no first half, there shouldn't even be a frame at all in fact. Something seems wrong with a frame being completely empty, which may have to do with the frame that has only half the callstack showing, though it's possible the half-callstack incidents might be my own issue (I'm not 100% sure yet).
,
Jul 12
This is driving me insane. The performance tab is just super flaky, not showing what's actually happening in our code. See here for a real-world example someone else posted on StackOverflow: https://stackoverflow.com/questions/46637939/chrome-performance-tab-reporting-hundreds-of-function-calls-that-didnt-happen What I see is a bunch of functions split into pieces, parts of the call stack completely missing, and parts of the existing callstack displayed in a different order than before when the code path is exactly the same. I am on a completely different system (macOS) than when I first reported this issue (Chrome OS), so it's not just my system. My current version of Chrome is 67.0.3396.99 (Official Build) (64-bit) on macOS 10.13.4 (17E199). Please Chrome team, this is a serious issue. It is causing a waste of developer time.
,
Jul 12
Related issue: https://bugs.chromium.org/p/chromium/issues/detail?id=768540
,
Jul 12
Oh wait, sorry, I'm using Electron, which has an older version of Chrome. It might be fixed already, based on https://bugs.chromium.org/p/chromium/issues/detail?id=768540.
,
Dec 19
Cannot reproduce it on codepen's testcase on M-73. As per comment 4, assuming it has been fixed since then. |
||
►
Sign in to add a comment |
||
Comment 1 by eostroukhov@chromium.org
, Jan 8 2018Status: Assigned (was: Unconfirmed)