https://bugs.winehq.org/show_bug.cgi?id=48482
--- Comment #11 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Federico Dossena from comment #8)
(In reply to Zebediah Figura from comment #7)
Sounds likely the program is running out of virtual address space. There may or may not be anything we can do.
Can you help me understand the issue? I noticed that the game's virtual memory is 3.2gb in size, but only a few hundred megabytes are actually used. Is this some kind of memory leak?
That suggests that something is allocating / reserving memory but not actually using it. I don't know that it tells us anything in particular though.
If the VIRT value goes up every time you go through the door then yeah, it does sound like a memory leak. It isn't immediately obvious what's leaking the memory though (e.g. is it the game itself or a specific Wine component?)
(In reply to Federico Dossena from comment #9)
Would an strace be useful to investigate this issue? I've been trying to use ltrace but it won't attach to the kotor process, only to wineserver. I want to intercept mallocs and frees to see if there's anything interesting
You could get a +heap trace, with additional channels (+wgl,+opengl ?) to figure out what's the source of those allocations. It's going to be pretty huge though. Another thing that might shed some light is /proc/<pid>/maps.