f6b7ec4da0
The reason of that is a number of cons strings in the app. The app constructs a json string and as a result v8 heap has a very long chain of cons strings. Profiler counts all these strings as plain String objects and assign the content of the strings as node names. It required O(n^2) time and O(n^2) memory. Solution: I introduced two new types, kConsString and kSliced string. They do not use the content of the string for names. So the problem disappeared. The heap profiler usability problem will be solved on Blink side. BUG=285770 R=yangguo@chromium.org Review URL: https://codereview.chromium.org/23460027 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16611 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 |
||
|---|---|---|
| .. | ||
| benchmarks | ||
| cctest | ||
| intl | ||
| message | ||
| mjsunit | ||
| mozilla | ||
| preparser | ||
| test262 | ||
| webkit | ||