> Ah, but it looks like the ArrayBuffer::New static constructor can
specify
that the array buffer should be created non-externalized. I'll give that a
shot,
because it means that the worker won't have to manage the memory.
SharedArrayBuffer will still have to be managed by the Shell, however.
the non-externalized ctor can't be used with shared array buffers, as that
would result in double-frees
Right, I only use it for transferring ArrayBuffers, not SharedArrayBuffers.
SABs
still need to have their memory managed externally.
https://codereview.chromium.org/1215233004/
--
--
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.
