Comment #2 on issue 2869 by [email protected]: Substring of huge string
retains huge string in memory
http://code.google.com/p/v8/issues/detail?id=2869
I briefly glanced the paper. It's not as easy:
- replacing a sliced string by a sequential string with same content
usually uses up more memory
- in return, releasing the backing store of the sliced string frees up
memory
It's really hard to tell whether flattening the sliced string is worthwhile
or not, especially since we don't have a good way to track what strings
refer to the same backing store. We had an attempt to flatten sliced
strings when GC happens, two years ago, but was rejected due to the fact
that it could cause an explosion on GC.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
