https://bugs.winehq.org/show_bug.cgi?id=53711
--- Comment #6 from Zeb Figura z.figura12@gmail.com --- (In reply to pandora.xero from comment #5)
(In reply to Zeb Figura from comment #4)
(In reply to joaopa from comment #3)
Unless developers request it, backtrace is pretty useless. Please attach the full console output. And install debug symbols.
I wouldn't say it's useless, actually (and in some cases it can even be more informative than console output). Ideally we'd like both where applicable.
In this case I've already discussed the bug with Chiitoo, and the problem is probably virtual address space exhaustion, although I've already forgotten some of the details.
considering all but one my backtraces seem to have a number over 0x78000000 on the top line (I'm guessing that's an address? I'm not sure how to read backtraces), physical address exhaustion would not surprise me. if I'm not mistaken, 32-bit x86 code restricts individual programs to no more than 2GB allocated. 0x78000000 is getting close enough to that boundary. I'm working on getting a 10TB HDD ready to handle all the console output, but for the time being I'm running the test again with just console output, and however many lines of scrollback I am afforded.
FWIW, in this case I wouldn't worry about getting full console output. Default console output may be helpful, but I think the cause is known.
If this is a virtual address space exhaustion issue, I feel the best way to determine if it is a wine issue or a program issue would probably be to see if I get the same results with the same level of utilization on a Windows machine. If it encounters the same or similar problems on windows with the same use case, it may be an issue with the game itself.
Sure. Although IIRC Chiitoo had reported this as a regression, right?