It seems to work for me.  I quadrupled the size of the splay benchmark
and I can run that without problems.  It tops out at over 250Mbytes in
the 64 bit version, around 140Mbytes in the 32 bit version (those fat
pointers take up space!).

2009/11/20 dracflamloc <[email protected]>:
>
> trace shows it gets to about 125MB and then can no longer free memory
> so it throws OOM.
> I've attempted to use --max-old-space-size but always get the same
> result
>
> I have tried this with 3339 and still it caps out at 125 in the trace.
>
> The thing is, I know where the memory is going (Lots of arrays),
> however I don't know why its capping out at such a small RAM usage.
>
>
> On Nov 20, 4:20 am, Erik Corry <[email protected]> wrote:
>> 2009/11/20 dracflamloc <[email protected]>:
>>
>>
>>
>> > #
>> > # Fatal error in (null)
>> > # Allocation failed - process out of memory
>> > #
>>
>> > Hello, I have v8 running in a VC++ 2005 console application. I'm
>> > running a script thats pretty simple, but is memory intensive. However
>> > the script always crashes after a few seconds while its creating
>> > arrays/objects with an out of memory error.
>>
>> > This computer has 3GB of RAM. How can I enable a script to access all
>> > available memory before throwing the OOM error, if it is indeed
>> > cutting off at 150MB?
>>
>> We had a bug until recently where you could get out of memory errors
>> without actually having run out of memory.  make sure you have a
>> version at least as recent as 3285 on the bleeding edge or 3333 on the
>> trunk.
>>
>> You can run the VM with --trace-gc to see how much memory it is actually 
>> using.
>>
>> There is an option --max-old-space-size for increasing the amount of
>> memory available to V8.
>>
>> I think the developer tools have some functions for tracing where
>> memory is going, but I am not personally familiar with them.
>>
>> --
>> Erik Corry
> >
>

--~--~---------~--~----~------------~-------~--~----~
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to