107676 2013-01-23 05:17:03 -0800 [chromium] Web Inspector: show when v8 has deoptimized 2013-04-05 13:01:44 -0700 1 1 1 Unclassified WebKit Web Inspector (Deprecated) 528+ (Nightly build) All All RESOLVED WONTFIX P2 Normal --- 107665 1 aerotwist webkit-unassigned apavlov john keishi loislo paulirish pfeldman pmuellr vsevik web-inspector-bugs yurys oldest_to_newest 814122 0 aerotwist 2013-01-23 05:17:03 -0800 Show when v8 has dropped off the fast path, i.e. a JS function has been deoptimized 815311 1 aerotwist 2013-01-24 03:46:18 -0800 More context: Right now we can run Chrome with specific flags which will dump out data about when v8 had to deoptimise a function. It would be super if we could include an additional record in the timeline view with a link to the specific JavaScript function that had to be deoptimised so that the developer could investigate. In a perfect world seeing the callstack that caused this to happen would also be extremely useful, as that would potentially ease the developer's burden in identifying what was actually different that may have caused the deoptimised code to be substituted back in. 826558 2 john 2013-02-06 10:56:07 -0800 CC 870018 3 timothy 2013-04-05 13:01:44 -0700 Chromium and V8 have left the building. Won't fix.