DescriptionDouble allocation size for special json strings on every resize (fixes
crbug 83877)
The issue was that with the relatively small start and increment size of the string we created a ton of string handles when scanning a large string with special characters (500k+ in this case).
In addition, since we can not be sure the the newly allocated string
is in newspace a check is introduced and if not a filler object is
inserted instead of shrinking.
Committed: http://code.google.com/p/v8/source/detail?r=8082
Patch Set 1 #
Total comments: 2
Patch Set 2 : '' #
Messages
Total messages: 3 (0 generated)
|