Bug 107676
| Summary: | [chromium] Web Inspector: show when v8 has deoptimized | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Paul Lewis <aerotwist> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | apavlov, john, keishi, loislo, paulirish, pfeldman, pmuellr, vsevik, web-inspector-bugs, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | |||
| Bug Blocks: | 107665 | ||
Paul Lewis
Show when v8 has dropped off the fast path, i.e. a JS function has been deoptimized
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Paul Lewis
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.
John McCutchan
CC
Timothy Hatcher
Chromium and V8 have left the building. Won't fix.