> It doesn't crash the app...it just won't ever move on from that line of code, waiting for V8. It's as if V8 decided to just not respond anymore but I'm not seeing any indication of an error. Also if I change this to an actual function call it will do the same thing (so not necessarily Promise related).
If i were you, i would suspect that some V8 background thread is waiting for a lock you/your v8 client has acquired .. I guess with the answer Jacob gave you, its clear that in predictable mode the v8 works with a single thread so that a lock on isolate acquired by your app becomes a non-issue. I do use v8 in a multi-thread env, but im doing in a way where theres only a background thread per-isolate, so the consumer threads (the frontend), have to dispatch to the backend threads to have some work done. I dont know if the context can be shared to more than one isolate(in my case i dont need), but if it does, you can have the best of both worlds.. just create a fixed ammount of isolate threads, and let only them manage the isolate, when theres a new request dispatch to the idle thread/isolate when the frontend asks for it. Maybe giving your needs, you cant design that way, but if you can, it would avoid locks on the isolate. -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
