I took a look into the WebKit issue, and I think that your problems are
related
to the currently broken External class: Although it is declared as a
subclass of
Value (i.e. promises to return a JavaScript object), Wrap/New can currently
return an internal object (a Foreign), which in turn causes the assertion
you
mention in the isssue to be triggered.
I think the current CL is probably not needed when we agree on the proposal
I
suggested last week: Add an API for accessing aligned pointers, making
External
a real Value, and deprecating the old unaligned pointer API plus
Wrap/Unwrap.
https://codereview.chromium.org/11087020/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
