On Fri, May 7, 2010 at 3:54 PM, Stephan Beal <[email protected]> wrote:
> elements themselves are destroyed. If your elements are C++ bound classes > then that probably isn't much work, whereas if they are plain JS objects it > would be problematic to capture the destruction for purposes of decrementing > the memory use. > OTOH, if the elements are "pure JS" then v8 already knows how much memory is used by them. You would only need to track the memory for any native libxml components which you keep around for the life of the parser. But if it becomes too much of a pain, just keep in mind that this level of management isn't technically necessary - it's just a way to allow v8 to help enforce any hard memory limit by making it aware of external allocation sizes. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
