Updates:
Status: WorkingAsIntended
Comment #1 on issue 2632 by [email protected]: Debug hitting
kHandleZap value
http://code.google.com/p/v8/issues/detail?id=2632
Hitting this check means there's a bug on the embedder side. V8 verifies
that it gets a valid object back from an API call, but in this case
apparently the embedder (i.e. node.js) is returning a dead handle. You
should fix node.js, there's nothing V8 can do about this (other than crash).
Blind guess: there's a C++ function somewhere that's bound to a JS object
and does something like:
{
HandleScope scope;
return v8::Foo::New(...); // Some call that creates and returns a handle.
}
When |scope| goes out of scope and is destroyed, the handle is zapped. If
this is the case, the fix is to use HandleScope::Close(my_handle) to
explicitly keep |my_handle| alive.
--
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/groups/opt_out.
