https://bugs.winehq.org/show_bug.cgi?id=55818
--- Comment #15 from Zeb Figura z.figura12@gmail.com --- If I go to Camelot, and also run around the city instead of standing still, I can trigger OOM here in less than 10 minutes. That's 10 minutes to get from about 3 GiB of used VM when I log in, to the full 4 GiB. For some reason there seems to be a bit of a bimodal distribution, or at least it's not consistent how long it takes—sometimes within like 2-3 minutes, sometimes 7-10, with the same build.
However, I also can reproduce this with 7.3 (using the same prefix, it works? The launcher is a black window but still responsive.) And at this point I'm kind of inclined to doubt the bisect result anyway; it'd be bizarre for that commit in particular to result in *more* memory usage. Not impossible, but weird.
If you watch VM usage while playing, do you see it steadily rise in this manner? How much VM are you starting with when you log in, and how long does it take to run out? What about with 7.3?
FWIW, for monitoring VM, I look for a process named game.dll and then use `watch -n 2 cat /proc/####/status`, with #### replaced with the (unix) pid. The most interesting line is VmSize. Other tools work though and should report the same results.