[Linux]Seemingly Random Crashes
computerquip
Join Date: 2013-09-11 Member: 188124Members, NS2 Playtester, Squad Five Blue, Retired Community Developer
Join Date: 2013-09-11 Member: 188124Members, NS2 Playtester, Squad Five Blue, Retired Community Developer
Every 30 minutes to an hour, I get a random crash. I can sometimes get 2 or 3 games in that time but it's quite annoying to continuously be kicked out of a game, especially if I can't rejoin on that specific server.
I have no way of providing any information as far as I know. "${XDGHOME}/.config/Natural Selection 2/log.txt" doesn't really provide much info. There's sometimes a window that pops up on crash but it's white with no title or responsible process name. I *think* the cause of the crash is awesomium but I have little to back that up. I'd run it in gdb if I could figure out the environment to run the game in without steam.
Anyways, just wanted to make sure this is known. It's common to everyone as far as I can see but I've almost never had a game run past an hour.
I run 64-bit Arch Linux, 32GB RAM @ 1866, an EVGA SuperClocked GTX 680, and AMD FX-8350.
EDIT: I run KDE with an OpenGL 3.1-based compositor. I find ALT+TABing in and out increases the chance of a crash but just based on speculation.
I have no way of providing any information as far as I know. "${XDGHOME}/.config/Natural Selection 2/log.txt" doesn't really provide much info. There's sometimes a window that pops up on crash but it's white with no title or responsible process name. I *think* the cause of the crash is awesomium but I have little to back that up. I'd run it in gdb if I could figure out the environment to run the game in without steam.
Anyways, just wanted to make sure this is known. It's common to everyone as far as I can see but I've almost never had a game run past an hour.
I run 64-bit Arch Linux, 32GB RAM @ 1866, an EVGA SuperClocked GTX 680, and AMD FX-8350.
EDIT: I run KDE with an OpenGL 3.1-based compositor. I find ALT+TABing in and out increases the chance of a crash but just based on speculation.
Comments
I don't think that's the problem anyways.
I don't think that 64-bit version would be a real solution. The game is awesome but I don't remember games requiring >4 Gb of RAM to work flawless. Except Minecraft maybe but that's Java which is memory-hungry by design. Its GC does defragment the memory IIRC so this kind of issue shouldn't happen on JVM. So the really real solution would be memory pooling or defragmenting. I've got no idea how it's implemented but they already have GC in place so it could be possible to defragment unused memory.
I think the game might have had a memory leak that was fixed with 258, but the random crashes are more akin of erronous programming, trying to access memory they have no business accessing, like a null or freed memory. Whatever will give you a nice segfault. It's impossible to say because I get no messages in the log and I have no means of running it through a debugger.
On a side note: There is absolutely no reason at all for a game to run 32-bits on PC today, if anything the 32-bit build should be an esoteric optional. I'm on a 64-bit system with 16G of RAM, even so the 32-bit multilibs work great with REALLY REALLY OLD games I still like to play.