http://bugs.winehq.org/show_bug.cgi?id=25428
--- Comment #6 from iliverez@gmail.com 2010-12-08 12:49:38 CST --- (In reply to comment #5)
Looks like the kernel doesn't want to map things under 37000000 or so. You could confirm this by running the Linux version of your app until you run out of space. If there's still a big chunk free after that it's a kernel issue.
When I run the gcc compiled version, on the 5GB RAM-PAE setup, it allocates 2GB without problem. I 've been using the 2GB max allocation value, because I think this is the memory limit for an application running with wine and I wanted to have a common ground for the test when it is gcc and winegcc compiled.
If I raise the max memory allocation value, I can go up to 3GB allocation, which is the max that a userspace app can get, no matter if the kernel is PAE or not. Also when the test is gcc compiled and runs with 5GB RAM available, the kernel maps things in the low memory range (see new attachment).
When I reach the 3GB limit for the test (gcc compiled, 5GB PAE), the system has about 1.5GB free RAM. So I guess that in this case, there is enough free memory available, but it is the userspace app memory limit which terminates the test.