viashimo

@sal_vager do you have links to upstream issues in the ksp bugtracker and unity (if public) that deal with this - I'd like to follow them there and contribute logs/testing if I can. Thanks!

In the 1.2 prereleases this is still happening regularly regularly. The following start seems to reduce but not eliminate the gnome crashes on ksp start: GDK_SYNCHRONIZE=1 nice -n 1 ./KSP.x86_64 -force-glcore -force-gfx-direct It would be good to see a proper fix for this (either in ksp or in unity, or both): gnome is one of the more widely used window managers.

From a couple of runs it looks like memory is the issue. The available system memory dries up quickly, swap increases, then everything is killed. After looking at https://linux-mm.org/OOM_Killer if a nice value is set on the process it will automatically double it's badness, so "nice -n 1 ./KSP.x86_86" seems like a good idea to begin with. I can't find a clean way to set a processes oomkilladj value immediately when starting it (maybe there's an environment variable somewhere?). However, I'm not entirely sure that it's oom-killer itself that destroys the parent process in my case. It seems that there would normally be a mention that oom-killer was invoked on a process in kern.log. At this point, 1.2 is coming soon (tm), so I may just wait for that. I'm not particularly enthused to switch desktop environments. If I get reliable starts with nice, I'll post again here. I have seen this affect other unity based games I have, so it makes sense that it's more an underlying unity issue than something specific to KSP. @sal_vager thanks for the extra suggestions too.

@sal_vager, thanks for the reply. Mea culpa for not looking more on the forums before asking. Unfortunately the oom killer doesn't help reduce the frequency of crashes. I generally get 1/6 attemps or so to start without crashing. I'll see if I can graph out memory usage to validate whether or not that is actually happening in my case.

Hi, since 1.1 I've experienced frequent issues starting KSP (both x86 and x64). I use debian 8 w/ gnome 3. KSP was initially installed through steam. Attached is an exerpt of a load from the syslog of the machine. There are two important things to note: 1) while the syslog says gnome-shell, I believe it's actually ksp running inside gnome. I often start KSP from a terminal for more output, and 2) KSP typically doesn't crash in this situation until the gnome session is completely terminated. From a user standpoint, ksp creates it's window and either before the loading screen appears or sometime during loading everything will flicker, the gnome borders will disappear and the screen will be replaced with a message saying that something had gone wrong in gnome and the session must be exited. No further user input can be made except to accept and destroy the session. This affects both modded & unmodded installs. It affects KSP when running from steam, or started without steam running. I experience the same issue with a single monitor and with two monitors. Has anyone else experienced similar issues, and if so, has anybody found work arounds or solutions? gpu: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) cpu: i7-3720qm @ 2.6ghz ram: 8gb system ram