Hi, thank you for your fast answer. I know that I have to use v8:Locker, and I use it at any place I am able to. But my problem is that v8-code itself uses "HandleScope::HandleScope" - this call is responsible for the ASSERT. And this code passage is NOT being locked. It occurs during v8::Script::Run, namely when the script throws an exception (please see the call stack in the email before).
Is it possible for me to avoid this situation without locking the execution of "v8::Script::Run"? Locking "Run" would mean to serialize the execution of all JavaScripts ( which would be very slow :( ) Or is the problem possibly a problem/bug of v8? Thank you again! Am Montag, 29. April 2013 13:26:35 UTC+2 schrieb Sven Panne: > > If you use v8::Locker anywhere, you have to use it everywhere. If you > that's not practicable for you, you'll have to ensure that at most one > thread is executing within each given Isolate by other means, i.e. locking > on your application side. > -- -- 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.
