Jochen, thanks for your help. Just hoping to get one more clarification:
On Tuesday, September 22, 2015 at 3:01:28 AM UTC-4, Jochen Eisinger wrote:
>
> Currently, the foreground tasks can run wherever the embedder wants to run
> them, but in the future, we might require that it's safe to access
Currently, the foreground tasks can run wherever the embedder wants to run
them, but in the future, we might require that it's safe to access the
given isolate from foreground tasks.
Background tasks can run wherever the embedder likes, and they will take
care themselves to use locks etc.. to
Ben, thanks for your response. Follow-up questions below:
> 2. Must foreground tasks be run with the isolate lock held?
>
> ...yes, you have to hold the lock.
>
Hmm, I just noticed that v8::platform::DefaultPlatform doesn't acquire the
lock to run foreground tasks. On the other hand, the V8
On Fri, Sep 18, 2015 at 4:01 PM, Bit Cortex wrote:
> V8 experts,
>
> I'm having trouble understanding the task scheduling requirements of the
> embedder's v8::Platform implementation. Some questions:
>
> 1. Is it a requirement that all foreground tasks for a given isolate be