Updates:
Status: Assigned
Cc: mvstan...@chromium.org
Comment #8 on issue 4121 by ish...@chromium.org: Regression: Memory leak
since at least 3.26.33
https://code.google.com/p/v8/issues/detail?id=4121
That's an allocation site pretenuring mechanism that causes this.
Currently we create literals array (which contains allocation sites each of
which in turn contain object/array literal boilerplates) per JSFunction.
This means that
1) for the code pattern #1 we have to create a LOT of objects,
2) since we have to keep dead allocation sites alive till next GC (because
of zombie problem) we have a memory consumption issue which looks like a
memory leak.
We could fix this by storing literal array per {NativeContext,
SharedFunctionInfo} instead of per JSFunction.
--
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
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
