Hi Deepti,
Thanks for your response.
On Wed, Sep 12, 2018 at 7:32 PM, 'Deepti Gandluri' via v8-users <
v8-users@googlegroups.com> wrote:
> If you are looking to track Wasm allocations, there is a counter on the
> Isolate that wasm memory allocations are registered
>
Looking at the code, it looks like --wasm_max_mem_pages limits the size of
a particular Memory object, but a script can always allocate multiple
objects / create multiple instances. I need to limit the script's total
memory usage...
I do need to track and limit per-isolate. But maybe I can use
Hi v8-users,
I noticed that WASM seems to ignore the ResourceConstraints I've set on my
isolate -- a WebAssembly.Memory object can grow to far beyond the heap
constraint I've set, and I don't see any constraint specific to WASM. The
JS code can, of course, specify a maximum memory limit when
