[x264-devel] Win32 large-address-aware?

[Jason Garrett-Glaser]

On Sat, Sep 12, 2009 at 1:34 PM, Jason Garrett-Glaser
<darkshikari at gmail.com> wrote:
> On Sat, Sep 12, 2009 at 1:08 PM, Jeppe Øland <uxorious at acon.dezign.dk> wrote:
>>> > Adding the option LargeAddressAware="2" to the vcproj linker section
>>> > would all but eliminate the problem for essentially all users.
>>>
>>> Perhaps you haven't thought your cunning plan all the way through, but
>>> x264 does not support any variants of the Microsoft VC series because
>>> said compilers do not support the language that x264 is written in
>>> (C99).  Additionally, practically all GUIs use an x264 build that is
>>> compiled with gcc.
>>
>> As you may be able to figure out, I have not actually compiled the code myself.
>> I found a problem with every executeable out there, and wrote about it
>> here so that hopefully somebody would fix it.
>> It seems like that it not likely to happen :-(
>>
>> Since there are vcproj files in the repository, I assumed that
>> somebody was compiling with VC - butI guess they are there for some
>> other reason?
>>
>> A quick google for "gcc largeaddressaware" shows that there is an
>> option for GCC/LD to do the same. --large-address-aware. (Since I have
>> never used GCC for Windows development, I am not sure if there are any
>> issues or if it's even the right thing).
>
> I just tested that here and it doesn't seem to help at all--x264 still
> crashes with a malloc failure at ~1.92 gigabytes memory allocated
> (Windows XP 32-bit).  I only have 2 gigabytes of RAM though, so I'll
> see if I get any better results on a machine with more RAM...
>
> Dark Shikari
>

According to #x264 IRC (where you should be on):

<Shinigami-Sama> Dark_Shikari: the OS still needs to set the /3gb switch
<Shinigami-Sama> in boot.ini append /3gb
<Shinigami-Sama> otherwise windows splits the 32bit address space 50/50

Dark Shikari