Status: New
Owner: ----
CC: [email protected], [email protected], [email protected], [email protected]
Labels: Type-Bug Priority-Medium

New issue 3012 by [email protected]: Interaction between GC heuristic and blink partition allocatior
http://code.google.com/p/v8/issues/detail?id=3012

See http://code.google.com/p/chromium/issues/detail?id=315082 for background.

Blink's partition allocator kills the process if more than 1GB is allocated in the same size class.

This change led to a situation where the GC heuristic was just a bit not aggressive enough to collect garbage in time. As a work around, I made StaticNodeList report the size of its node list as external memory to v8, however, this has a measurable perf impact.

This raises the question whether we should instead tune the v8 gc heuristics.


--
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/groups/opt_out.

Reply via email to