https://bugs.winehq.org/show_bug.cgi?id=53711
--- Comment #13 from pandora.xero@gmail.com --- (In reply to Zeb Figura from comment #12)
I hate to say it, but I don't think +relay is at all useful for this kind of bug. Nor would I even use the entire +d3d log from an hours-long session, probably :-/
One thing I had asked Chiitoo for was essentially a monitoring of adapter_adjust_mapped_memory(), to see if it was gradually increasing over some long period of time. I remember that he responded, but I've forgotten what the logs looked like by now.
Along the same lines it may make sense to e.g. simply watch the process VM use, via top(1) or /proc/<tid>/stat, or something like that.
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.
I'm going to run this game on Windows for a few days... no third-party software, just the game, and task manager on monitor 2. It doesn't make much sense to keep on testing if we don't have some sort of baseline to test against. And I'll be the first to admit my use case on the game is more than slightly niche.