Comment #1 on issue 3666 by [email protected]: Garbage Collection
Fails to collect on time
https://code.google.com/p/v8/issues/detail?id=3666
This doesn't make sense. If V8 itself is crashing because it's running into
the max heap size limit (which is the only "process memory limit" I know of
in Chrome), then manually triggering more GC cycles earlier shouldn't help,
because maximally-aggressive "last resort" GC cycles are performed
automatically when heap space is low.
If you mean that you're seeing memory *growth* in Chrome, but *crashes* in
your custom browser, then you'll probably just have to configure V8's heap
limit. Try the --max_old_space_size flag. Note that it only controls one
(albeit the biggest) part of the heap's size, so set it to a value that
leaves some room for the rest.
Any chance you could provide a link to your app (and repro instructions for
the crash) so we could take a look at what's happening?
--
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.
