> However, it clears microtasks for _all_ contexts. Presumably that's
> not what you want.
Yes, but I now guess it won't happen that microtasks of different
contexts exist at the same time. We will keep executing js code
of context-1 until async API is called, and then we switch to
context-2, befo
On Wed, Oct 26, 2022 at 5:29 AM Jianyong Chen wrote:
>
> Thanks, Ben.
>
> > Assuming your execution contexts don't interleave (context A can't
> > call functions from context B), then all you have to do is place
> > CancelTerminateExecution calls in the right spots.
>
> Yes, we do not have context
Thanks, Ben.
> Assuming your execution contexts don't interleave (context A can't
> call functions from context B), then all you have to do is place
> CancelTerminateExecution calls in the right spots.
Yes, we do not have contexts interleaving(but context switch due to
async calls).
As to the "r
On Tue, Oct 25, 2022 at 3:41 AM Jianyong Chen wrote:
>
> I also have these questions and if any v8 experts(or people with
> replated knowledge/experience) see this post please give us some
> information about them.
>
> We are embedding v8 into our HTTP server and creating one isolate
> per thread,
