Bug 19230
| Summary: | Web Inspector: profiler accrues time to (idle) if profiling is started and finished within the same function | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kevin McCullough <kmccullough> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | burg, graouts, joepeck, jonowells, mattbaker, nvasilyev, timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Kevin McCullough
SquirrelFish changed the information passed into the profiler when the profiler starts. The ExecState that is passed in does not have a stack trace to follow and so if we do not return from the function that called console.profile() the profiler does not know which node to assign its currently executing time to and so it goes to (idle)
See WebCore/manual-tests/inspector/profiler-test-simple-no-level-change.html
<rdar://problem/5958770> JSProfiler: Time incorrectly given to (idle) if profiling is started and finished within the same function.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brian Burg
No idea if this is still an issue, but migrating so someone might look at it.
Timothy Hatcher
We don't have idle anymore.