I'm not a V8 expert, but I'll try to answer this.
* Each Isolate can only be entered by a single thread at a time.
* However, Isolates can be migrated between threads. For example, Node.js
only uses a single Context, but has multithreading of background
(non-script) code like I/O. This is simi
maybe an alternative idea: i've read that it is possible to create multiple
contexts within one isolate.
so instead of multiple isolates, i could create only one, and create
multiple contexts.
Are those context separated from, or can they interfere with eachother?
and what are the traps you nee
On Fri, Apr 29, 2016 at 2:03 PM, Joris Wijnant
wrote:
>
> What is the reason that is reserves 16 MB?
> I know that reserving some extra space can be for performance, that way
> you don't need to request more if you ran out.
> But what is the reason for 16 MB, why not less?
>
AFAIK that's what Ne
What is the reason that is reserves 16 MB?
I know that reserving some extra space can be for performance, that way you
don't need to request more if you ran out.
But what is the reason for 16 MB, why not less?
and can I possibly lower it, to lets say 5MB?
--
--
v8-users mailing list
v8-users
That stack trace indicates you ran into DCHECK(IsReserved()); in
VirtualMemory::address(). That check would fail if the previous mmap() call
failed to reserve memory, which happens when the process's virtual memory
address space is exhausted.
You didn't specify which V8 version you're using, but ch
For some reason can i go to 700MB, instead of the 300MB earlier, but i
don't know what changed :s
I'm reaching 140 isolates, which is coming closer, but not enough.
Also each isolate only contains a few objects, so 10MB should be more than
enough.
This time it crashes by raising a SIGABRT.
stac
