[+v8-users, chromium-dev to BCC]
There is no single bottleneck for JS object allocation; objects are created
all over the place. As a starting point, you can look at all
CodeStubAssembler::AllocateJS* and Factory::NewJS* functions. I don't know
whether that set spans all JS object allocations, but
Hi Philip,
Thanks for the report. Would you mind coping it to
https://bugs.chromium.org/p/v8/issues/entry so that is tracked properly?
V8 is trying to grow the heap as expected, but one of the fs stream
operations is allocating memory outside the heap and reporting it to V8
using AdjustAmountOfEx