https://bugs.winehq.org/show_bug.cgi?id=44246
--- Comment #5 from Alex S iwtcex@gmail.com --- (In reply to Adrien Fernandes from comment #4)
Three years now I'm having this issue and it has never been fixed.
This is actually a somewhat infamous issue and it's much older than that. The usual workaround involves either setting LARGE_ADDRESS_AWARE flag on the executable (which tells Wine to apply a different memory allocation limit) or patching Wine to the same effect. Proton even has a convenient PROTON_FORCE_LARGE_ADDRESS_AWARE environment variable for that matter.
In my experience this workaround results in lower virtual memory allocation by roughly 700 Mb - 1 Gb. It's not clear to me how it does that, it's really not supposed to.
Why I can play Call of Duty 4 on GNU/Linux but not on FreeBSD with the exact same hardware ?
Is there a noticeable difference in virtual memory allocation?