https://bugs.winehq.org/show_bug.cgi?id=55818
--- Comment #18 from Zeb Figura z.figura12@gmail.com --- (In reply to Tom M from comment #17)
I got the game to lock up. When it locked it said: VmSize: 4194228 kB
Which I guess is the absolute limit of a 32-bit app?
Close enough to it, yes. (The actual limit is 4194304 kB.)
(In reply to Tom M from comment #16)
Hi,
I played in Molvik (one of the battlegrounds) for 3 hours 41 mins. Bug did not trigger once. VMSize fluctuated between 2.3 GB and 2.89 GB. Towards the end of the time period it got up to 2.98-3.09 GB but the game stayed running.
I assume it was 2.3 when you logged in, then? By "fluctuated" was it always increasing, or did it actually go up and down? Which version was this?
Right now there are three questions I'd like to resolve:
* What's necessary to trigger the regression? For me at least, simply testing with 7.3 and 7.4 (or current git), simply by running around Camelot, doesn't show a clear difference in behaviour.
* Is the bisect actually correct? If the behaviour is very variable from run to run, that means the bisect could have gone wrong. Getting a better handle on how memory usage looks like as the game runs (rather than just "does it run out") may also help the bisect to be done more reliably.
* Are we running out of memory because memory is leaking (faster) or because base memory usage is higher to start with?