Bug 19230 - Web Inspector: profiler accrues time to (idle) if profiling is started and finished within the same function
Summary: Web Inspector: profiler accrues time to (idle) if profiling is started and fi...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2008-05-23 17:22 PDT by Kevin McCullough
Modified: 2014-12-19 11:08 PST (History)
8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin McCullough 2008-05-23 17:22:07 PDT 
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.
Comment 1 Brian Burg 2014-12-17 16:50:43 PST 
No idea if this is still an issue, but migrating so someone might look at it.
Comment 2 Timothy Hatcher 2014-12-19 11:08:51 PST 
We don't have idle anymore.