On 2014/04/30 19:32:06, Hannes Payer wrote:
I cannot think about a reason why the limits make sense
--max-new-space-size makes sense when you want to ensure that even a
relatively
short-running test triggers one or more allocation failures and resulting
scavenges. Especially for the regression tests, I would guess that the flag
was
necessary to reproduce the original bug.
--max-old-space-size makes sense when a test tests OOM behavior, but it
doesn't
look like any of the tests you modified did that, so it's probably fine to
remove that flag.
https://codereview.chromium.org/263703003/
--
--
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.
