http://bugs.winehq.org/show_bug.cgi?id=30849
--- Comment #66 from Jason Parker north@ntbox.com 2012-06-07 13:39:52 CDT --- (In reply to comment #65)
Created attachment 40436 [details] address space reporting tweak [v2]
(In reply to comment #64)
... Well, I think that it's relevant to know that it's the reporting of the address space that's killing things - not the actual internal use. Also, I thought there was a max 3 GB limit on user address space with 1 GB reserved for the system?
Using the the "Memory Limits for Windows Releases" table from MSDN I've constructed a revised patch (attached). I think the problem might be a function of: "true" 32, WoW64, and IMAGE_FILE_LARGE_ADDRESS_AWARE.
That makes sense to me. Though I think your 0xb... should be 0x8...?