Again on trunk, I can only consistently reproduce this by using one thread 
to compile a script, exit the isolate, and then using another thread to 
enter the same isolate and create a context.  That'll hit 
bootstrapper.cc:2610 check.HasOverflowed().

Does that indicate a problem somewhere?

On Friday, March 14, 2014 4:51:48 AM UTC-7, Ben Noordhuis wrote:
>
> On Fri, Mar 14, 2014 at 1:57 AM, Jane Chen <[email protected]<javascript:>> 
> wrote: 
> > Ben, 
> > 
> > Can one Isolate have more than one Context?  Say if I use one Context to 
> > construct a Script, and later create another Context to execute that 
> Script 
> > in the same isolate, would that cause the intermittent empty Context 
> problem 
> > described above? 
>
> An isolate can have many contexts so yes, that should work if you use 
> Script::New(). 
>
> (I think Script::Compile() should work too but I'm not 100% sure about 
> that.) 
>
> > I'm seeing Genesis::Genesis() initializes _result to null when I get an 
> > empty Context handle. 
> > 
> > When I save the context I use to compile the script with the Isolate, 
> and 
> > use that to run the script, I don't run into this issue.  I only run 
> into it 
> > when I need to create another Context after the script is compiled. 
>  Problem 
> > is I want to start with a new context every time for execution. 
>
> Can you post example code?  Not just snippets, please, something that 
> compiles. 
>
> I can think of a number of reasons why you get the behavior that 
> you're seeing but without seeing the code, I can only guess. 
>
> What version (or versions) of V8 are you targeting? 
>

-- 
-- 
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/d/optout.

Reply via email to