Bug 61184
| Summary: | Web Inspector: [JSC] Searching in a bottom-up view of a large CPU profile overloads system | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Mikhail Naganov <mnaganov> |
| Component: | Web Inspector (Deprecated) | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | apavlov, bweinstein, ggaren, joepeck, keishi, loislo, mark.lam, oliver, pfeldman, pmuellr, rik, yurys |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://v8.googlecode.com/svn/data/benchmarks/current/run.html | ||
Mikhail Naganov
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brian Burg
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.