Status: Untriaged
Owner: ----
New issue 4409 by [email protected]: ArrayBuffer API triggers unnecessary
mark-and-sweep events
https://code.google.com/p/v8/issues/detail?id=4409
Version: 4.4.63
OS: all
Architecture: all
What steps will reproduce the problem?
- reproduction code and instructions at
https://github.com/mlogan/arraybuffer-gc
What is the expected output?
- v8 should not repeatedly trigger mark-and-sweep gc, as the amount of
external memory is not increasing.
What do you see instead?
- v8 *does* repeatedly trigger mark-and-sweep gc.
The root cause is that v8 adjusts the amount of external memory upward when
creating a new internalized ArrayBuffer (via SetupArrayBuffer in
runtime-typedarray.cc) but does not adjust downward when externalizing that
same ArrayBuffer.
See also: https://groups.google.com/forum/#!topic/v8-users/lxcOvRpdlUk
--
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/d/optout.
