Updates:
Cc: [email protected]
Comment #5 on issue 4392 by [email protected]: TurboFan/asm.js memory not
immediately released
https://code.google.com/p/v8/issues/detail?id=4392
This isn't compilation memory. It's V8 parser / scope analysis memory,
which happens before any compiler gets to the code.
The main issue is the zone memory (i.e. C++ land) memory allocated by the
parser and scope analysis for the module function. This ultimately turtles
down to C++ new, which I think Blink has a hook to manage. It might be that
Blink doesn't recycle this malloc'd and freed memory quite fast enough and
that your experiments with waiting triggered a cleanup.
We probably need to ask an expert on Blink memory management, so I'll cc
[email protected].
On the V8 side, we are working on reducing the memory used by the parser by
parsing the nested functions in different zones.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" 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.
