On 2015/05/19 14:55:02, Hannes Payer wrote:
On 2015/05/19 13:09:54, rmcilroy wrote:
> -jochen, +hpayer.
>
> Fix typo in the description.
>
> Otherwise seems reasonable to me, but I'll let Hannes approve incase
there
is
a
> reason why it's only returning the 4 spaces currently.
Available for lo space returns the amount of memory available by the
system
memory allocator. Do you really want that?
The only use case of this method right now is at
v8IsolateMemoryDumpProvider.
This has an "other spaces" category which shows the memory missed out by the
HeapSpaceStatistics() api (in case more spaces are added in future and the
space
stats api is not updated). When I calculate the difference between
heap::Available() and sum of available from spaces, it turns out to be
negative
because lo_space isn't counted. What do you suggest is the solution?
https://codereview.chromium.org/1141693003/
--
--
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/d/optout.
