V8 suffered from a virtual address space leak which was fixed and
backmerged to 57 (https://bugs.chromium.org/p/v8/issues/detail?id=5945).
Awesome it works for you now.
On Thu, May 11, 2017 at 7:04 PM Andre Cunha
wrote:
> I have repeated the tests in V8 5.8.283.38,
I have repeated the tests in V8 5.8.283.38, and indeed the problem is gone.
The amount of virtual memory remains stable over time.
With regard to the cause of the problem, I managed to create a similar
situation (increase in virtual memory consumption without increase in
actual memory usage)
On Thu, May 11, 2017 at 3:38 PM, Jochen Eisinger
wrote:
> Thank you for the detailed bug report.
>
> I tried reproducing this on the latest version of V8, but couldn't observe
> the behavior you described.
>
> Have you considered updating to at least the latest stable
Thank you for the detailed bug report.
I tried reproducing this on the latest version of V8, but couldn't observe
the behavior you described.
Have you considered updating to at least the latest stable version of V8?
On Wed, May 10, 2017 at 7:50 PM Andre Cunha
wrote:
I've managed to reproduce the problem using just V8's hello_world example
(source code attached). I just added a loop around the creation and
destruction of the Isolate (this is what happens in each cycle of my stress
test). When I run the process and monitor it in "top", the RES column stays
@Michael Lippautz, I'll try adding a breakpoint if AllocateChunk returns
NULL; hopefully, I'll get more information about the problem.
@Jakob Kummerow, yes, I'm calling Isolate::Dispose() in every isolate after
using it. I'll also observe the VIRT column and see if it shows any
abnormality.
My guess would be an address space leak (should show up in the "VIRT"
column of "top" on Linux). Are you calling "isolate->Dispose()" on any
isolate you're done with?
On Mon, May 8, 2017 at 4:01 PM, Michael Lippautz
wrote:
> V8 usually fails there if it cannot allocate a
V8 usually fails there if it cannot allocate a 512KiB page from the
operating system/
You could try hooking in AllocateChunk [1] and see why it is returning NULL
and trace back through the underlying calls.
Best, Michael
[1]:
Hello,
I have embedded v8 into a project for the company I work for, and during
some stress tests, I've encountered a weird out-of-memory error. After
considerable investigation, I still have no idea of what might be going on,
so I'm reaching out to you in hope of some insight.
So here is a