JSString::resolveRope() should report extra memory cost to the heap.
authorcommit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 28 Feb 2012 16:02:02 +0000 (16:02 +0000)
committercommit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 28 Feb 2012 16:02:02 +0000 (16:02 +0000)
commit3fe31f6bdf5935f05f7888babd294da3f02b02a7
tree10bb99d1a1b8b5e04039e4401097055f84a005dd
parenta37f90a39ccf153040b0f53ce36f95c95ecd00d1
JSString::resolveRope() should report extra memory cost to the heap.
https://bugs.webkit.org/show_bug.cgi?id=79555

Patch by Yong Li <yoli@rim.com> on 2012-02-28
Reviewed by Michael Saboff.

At the time a JSString is constructed with fibers, it doesn't report
extra memory cost, which is reasonable because it hasn't allocate
new memory. However when the rope is resolved, it should report meory
cost for the new buffer.

* runtime/JSString.cpp:
(JSC::JSString::resolveRope):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@109105 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/JavaScriptCore/ChangeLog
Source/JavaScriptCore/runtime/JSString.cpp