https://bugs.winehq.org/show_bug.cgi?id=43545
Robert Xiao nneonneo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nneonneo@gmail.com
--- Comment #3 from Robert Xiao nneonneo@gmail.com --- It sounds like this is the same memory exhaustion issue that causes my client to crash after ~1.5 hours on macOS; it's presumably more severe on Linux because of the 1GB reserved for the kernel high memory (0xc0000000~0xffffffff).
On macOS the game starts with 2.2 GiB of virtual memory allocated; as soon as a game starts, this increases to about 2.8 GiB. There's a slow memory leak that causes the game to eventually consume all 4 GiB of VM space, and subsequently die. Maybe I will file a bug for that - so far I do not know where the problem is.
Before it crashes, perhaps a look at /proc/<wine-pid>/maps could be instructive, in case there's some large object that's loaded to the address space that doesn't need to be. The hope is that we could reduce the initial address space memory pressure enough to make the game runnable for a longer period of time (although any memory leak will still eventually kill the game).