program is native function calls, often poorly performing animations look like this, the connection is not immediately apparent because the calling function looks like it takes a disproportionately and innocently small amount of CPU time.
Admittedly I did not check further so maybe i'm wrong, but that function is at the top of the list for the JavaScript code, if it's GC the connection is easier to establish because you can look at the objects on the heap and see if they are created by that function... if it's native canvas or webGL on the other hand I find I usually have to change the code to find the relationship... maybe there are more advanced ways, I know there is way more to chromiums dev tools that what I use.
I too pissed to dig deeper... why couldn't the site authors be bothered to properly debug some animation code that is clearly runaway.
Typinganimationframe wasnt on the list for me. Just lots of calls using small amounts of time. Its the animation thats causing the gc and program time.
Admittedly I did not check further so maybe i'm wrong, but that function is at the top of the list for the JavaScript code, if it's GC the connection is easier to establish because you can look at the objects on the heap and see if they are created by that function... if it's native canvas or webGL on the other hand I find I usually have to change the code to find the relationship... maybe there are more advanced ways, I know there is way more to chromiums dev tools that what I use.
I too pissed to dig deeper... why couldn't the site authors be bothered to properly debug some animation code that is clearly runaway.