On Wed, Aug 12, 2009 at 11:32 AM, Kevin Millikin <[email protected]>wrote:
> There's also an API call to change those parameters. A few months ago > (probably about 6 I guess) it was working, from the command line, with and > without snapshots. OK - good to know. > > What doesn't work and probably crashes is if the initial heap is not big > enough to bootstrap the VM. This can even happen if the heap is strictly > big enough but its "geometry" is wrong---if the old space is taken up by the > initial paged spaces we will not be able to allocate large objects. > > Could that be what you're running into? > I don't think so - I was using pretty large sizes (e.g. 8MB in the renderer for semi-space and 1MB in the browser). I'll see if I can isolate something better. thanks Mike > > > On Wed, Aug 12, 2009 at 7:28 PM, Mike Belshe <[email protected]> wrote: > >> In the browser heap we use a "little" V8 instance for the Proxy PAC code. >> Right now, it gets tuned with the same heap parameters as the renderers. >> But I'd like to tweak it way down because the amount of JS work that it >> does is small. >> >> However, using the command line options doesn't seem to work - if I use >> the --new_space_size and --old_space_size flags to tweak down the browser >> process' sizes, V8 crashes. >> >> I believe this is because you can't use the command line options with >> snapshotting. Is this true? >> >> If so - is there a way we can use different heap sizes and still use >> snapshotting? >> >> Thanks, >> Mike >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
