Posted April 16, 2016
majkif: Am I the only one who gets crazy memory leaks on Linux? Game eats up RAM every time opens new encounter, but never release it. Super fast game eats up few GB of RAM.
Does version 321 work better for you?darktjm: Wouldn't surprise me, although I didn't notice it myself. The latest patch (gog #19, "build #309") is actually the first version that is playable on my machine. Previous versions went from taking locks on kbd and video and then hanging after 5 minutes of run time, to active random terrain texture, to now being playable. I have too much other stuff to do than to track down causes and submit a useful bug report, though. I guess I should just be happy it finally works at all. It still has bugs: painfully slow zoom in/out when starting an expedition or discovering a new location of interest, never removing the "Start Encounter" button for the duration of an encounter (just clearing the button text and making it inactive), claiming I have 0MB of dedicated video memory (I suppose that could be, depending on how they compute it, since I use a laptop). I also sort of consider it a bug when a game puts writable stuff in the game dir, rather than in /tmp or in the user's home dir (this one puts stuff in "userdata" under the game dir). I like to install Linux-native games owned by root in /usr/local, which is defeated by games doing this crap (and, like Shadowrun, giving no indication that's why it freezes at a random spot during game play or loading). Sorry for the rambling non-response. Can't tell by your post date if you are actually using the latest version or not, given it claims numerous memory fixes.
Can you try version 321 and see how it goes for you?Post edited April 16, 2016 by JudasIscariot