What steps will reproduce the problem?
1. Gather a CPU profile from V8 benchmarks site.
2. Try to search in bottom-up view.
Search hogs all time of a CPU core and finally stops with no results.
DevTools stops working after that. Analysis shows that this is due to V8's
heap got exhausted by trying to build a bottom-up tree from a top down.
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, which can grow
up V8's heap to its limit. JSC doesn't impose heap size limit, so searching in
the same tree in WebKit just eats up a enormous amount of memory, but
It seems that an approach to maintaining calls tree needs to be reworked in
Created attachment 94204 [details]
Comment on attachment 94204 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=94204&action=review
> + // FIXME: implement building bottom-up profiles in C++ code,
Please file a bug against JSC and put its number next to the FIXME.
Manually committed: http://trac.webkit.org/changeset/86947
2011-05-20 Mikhail Naganov <firstname.lastname@example.org>
Reviewed by Yury Semikhatsky.
Web Inspector: [Chromium] Use bottom-up CPU profile tree built in VM,
instead of building it on Inspector's side.
(In reply to comment #2)
> (From update of attachment 94204 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=94204&action=review
> > Source/WebCore/bindings/js/ScriptProfile.cpp:71
> > + // FIXME: implement building bottom-up profiles in C++ code,
> Please file a bug against JSC and put its number next to the FIXME.
Oh, sorry, I've already had an issue created: https://bugs.webkit.org/show_bug.cgi?id=61184
But I forgot to put it into fixme.