On Tuesday, April 23, 2013 9:18:36 AM UTC-7, Jakob Kummerow wrote: > > > >> >>> (Running in Debug mode should quickly ascertain whether this is the >>> cause of the problem.) >>> >> >> Hmm, what should I be looking for ? I'm running in debug, but not quickly >> ascertaining ;-) >> > > The handle should have been zapped upon destruction of the HandleScope, > rendering its internal pointer obviously invalid. Then, some CHECK() should > have failed due to this zapped pointer. >
Oh! Yes that totally happened. But I thought this was some kind of bug in V8! The code crashed with a stack pointing to: OPEN_HANDLE_LIST(MAKE_OPEN_HANDLE) The crash message mentioned allow_empty_handle || that != NULL But these two bits of information did not help me since they did not seem to have anything to do with my code. jjb > If that didn't happen, then you may have found a loophole in V8's > zapping/checking machinery... > You're not overriding the 'v8_enable_extra_checks' GYP variable, are you? > > >> >> jjb >> >> -- >> -- >> v8-users mailing list >> [email protected] <javascript:> >> http://groups.google.com/group/v8-users >> --- >> You received this message because you are subscribed to the Google Groups >> "v8-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" 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.
