Comment #3 on issue 4201 by [email protected]: ArrayBuffer external
memory not freed during mark-sweep
https://code.google.com/p/v8/issues/detail?id=4201#c3
The following revision refers to this bug:
https://chromium.googlesource.com/v8/v8.git/+/839170e78536f2867ab6e42872dfa87bef0e5959
commit 839170e78536f2867ab6e42872dfa87bef0e5959
Author: jochen <[email protected]>
Date: Mon Jun 22 13:24:40 2015
Keep track of ArrayBuffers based on collector type, not space
Since Mark/Compact also collects garbage in the new space, we can't just
free old space ArrayBuffers during MC - otherwise we run the risk of
never freeing new array buffers
BUG=v8:4201
[email protected]
LOG=n
Review URL: https://codereview.chromium.org/1199913002
Cr-Commit-Position: refs/heads/master@{#29190}
[modify]
http://crrev.com/839170e78536f2867ab6e42872dfa87bef0e5959/src/heap/heap.cc
[modify]
http://crrev.com/839170e78536f2867ab6e42872dfa87bef0e5959/src/heap/heap.h
[modify]
http://crrev.com/839170e78536f2867ab6e42872dfa87bef0e5959/src/heap/objects-visiting-inl.h
--
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.
