Since V8 does not know how the memory backing an ArrayBuffer has been > allocated in this case, there is now good way for V8 to free it. >
This doesn't make sense. A part of v8::ArrayBuffer::Allocator is a Free method. When you pass an allocator to v8::V8::SetArrayBufferAllocator, you are giving V8 all the tools to both allocate and deallocate memory for an ArrayBuffer. I see absolutely no reason why you can't make the ArrayBuffer take ownership of the memory again when you are done with it. It took ownership when it was created. If it can't take ownership again, this sounds to me like a limitation of it's implementation, not an actual virtue of its design. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" 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.
