Bug 61184 - Web Inspector: [JSC] Searching in a bottom-up view of a large CPU profile overloads system
Summary: Web Inspector: [JSC] Searching in a bottom-up view of a large CPU profile ove...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (Deprecated) (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://v8.googlecode.com/svn/data/ben...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-20 05:32 PDT by Mikhail Naganov
Modified: 2014-12-12 14:09 PST (History)
12 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 Mikhail Naganov 2011-05-20 05:32:45 PDT 
What steps will reproduce the problem?
1. Gather a CPU profile from V8 benchmarks site: http://v8.googlecode.com/svn/data/benchmarks/current/run.html
2. Try to search in bottom-up view.

Search hogs all time of a CPU core.

This problem originates from the fact that in WebKit Inspector the bottom 
up tree is built dynamically from the top down tree. Thus, to perform a 
search in a bottom up tree, it first needs to be fully built, as a result,
Inspector eats up an enormous amount of memory.

It seems that an approach to maintaining calls tree needs to be reworked in 
WebKit Inspector.

Consider https://bugs.webkit.org/show_bug.cgi?id=24604 when implementing,
to avoid incorrect calculation of execution times.
Comment 1 Brian Burg 2014-12-12 14:09:48 PST 
Closing as invalid, as this bug pertains to the old inspector UI and/or its tests.
Please file a new bug (https://www.webkit.org/new-inspector-bug) if the bug/feature/issue is still relevant to WebKit trunk.