Comment #3 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
The point here is: On one hand, our sliced strings are an optimization for
one kind of use cases (probably chosen from one of the "great" benchmarks
we care about), on the other hand, sliced strings in their current naive
form are a source of unlimited(!) space leaks for other use cases. So the
question is: Can we mitigate the latter problem at least a bit? While a
general solution might involve quite some work, solving easier cases might
be relatively straightforward, e.g. when a single sliced string is the only
reason for keeping another string alive.
We are not the first ones encountering this kind of problem, so there
should be a variety of solutions already out there. Let's keep this issue
open.
--
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.
