Lacking any proof, I somehow doubt that the problem is in v8: :-) Chrome uses the aligned pointer API quite heavily for some time now without any known problems. Could you set a breakpoint in Utils::ReportApiFailure and check that the value of the pointer when the error happens? The code path leading to the fatal error is so simple (basically an IsSmi call plus a check) that it's hard to believe that it works only partially. Famous last words... ;-)
As you've probably figured out, using External is not really cheap, because it involves allocating 2 objects: One JavaScript object with a hidden field containing a Foreign, see Heap::AllocateExternal. -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
