https://bugs.winehq.org/show_bug.cgi?id=53711
--- Comment #15 from pandora.xero@gmail.com --- (In reply to Zeb Figura from comment #14)
(In reply to pandora.xero from comment #13)
This may be true... and indeed a trivial task. but if there is, for example, a memory leak, how do we know just by watching the VM use what's causing it?
The VM Use will tell us how much RAM the total process is using... but not necessarily what component of the process is using so much.
We don't, but I also don't remember if it was definitively confirmed that the crash is coming from a memory leak. It could be some very rare race, I guess.
Ran it until it crashed - here's the output from top
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 18065 xero 20 0 4174044 497084 94132 S 0.0 0.8 125:46.42 pol.exe
VIRT jumps about 20MB every time I switch characters.
My baseline on Windows only went as high as about 320MB Used - but I'm guessing that number only reflects the equivalent of the RES column here - and that was after much more activity, much more play time, and many more character changes.
I'm unsure as to what's causing VIRT to balloon in size like so. I don't know if this is a factor or not, but the system in question has no swap partition/file, and 64GB of RAM total.