[v8-users] Re: About to go (more) insane. SegFault calling GetOwnPropertyNames().

I gave up. After fixing a few Local returns that weren't Escape()'ed I ended up with the code blowing up for not having a HandleScope... Which made no sense because where it blew up was on the line where I had created an EscapableHandleScope. I worked around the entire mess of trying to pass

Re: [v8-users] Deadlock when calling TerminateExecution

I haven't heard of a similar issue so far. If you can't get a stacktrace of all threads when this happens, you're next best option would be to run with thread sanitizer support compiled in (requires clang) On Wed, Feb 3, 2016 at 5:55 AM David Lattimore wrote: > My application

Re: [v8-users] Isolate->Dispose() causes crash only when Math.random() is used

you stack-allocate the ArrayBufferAllocator, so it'll get destructed at the end of the Initialize() method. You should allocate it on the heap instead, so it outlives that method. best -jochen On Mon, Feb 1, 2016 at 10:17 PM George Corney wrote: > Hey, > > I'm struggling

Re: [v8-users] Isolate->Dispose() causes crash only when Math.random() is used

Yep, that was it! Thanks for your help Jochen! On Tuesday, February 2, 2016 at 8:48:56 AM UTC, Jochen Eisinger wrote: > > you stack-allocate the ArrayBufferAllocator, so it'll get destructed at > the end of the Initialize() method. > > You should allocate it on the heap instead, so it outlives