* Note that the callstack is from my original error, not the test, but
it is the same error, only the origin changes.
Thanks for your help.
NicDex
--
v8-users mailing list
v8-u...@googlegroups.com
http://groups.google.com/group/v8-users
Judging from the stack trace only, are you sure you make a proper
reference to you object and it doesn't get garbage collected?
yours,
anton.
Overall code looks mostly fine.
One thing was noted by Matthias---Persistent handle leakage.
Overall, you can use GetPointerFromInternalField and
SetPointerToInternalField which are faster and imho easier to use (a
lot of code would just go away).
Another thing you might want to fix: it's usually a bad idea to access
internal fields on args.This(), typically you should do that on
args.Holder(): This() is the object on which the property was accessed
while Holder() points to object which was created with your custom
function. Example:
myClass = new MyClass();
o = { __proto__: myClass };
Now if you do o.gridX, args.This() should point to o while
args.Holder() should point to myClass.
In your sample This and Holder should be the same, but I wonder if
it's the case when you get a crash.
And the last: zero length arrays are prohibited. Again I think it's
just a matter of reduction, but just in case.
yours,
anton.