Crashes in Editors

[SatanSoldier]

Linux Mint 17.2 x64

Native Steam/Default KSP

I'm getting crashes in both the SPH and VAB upon selecting a new part to add. This is repeatable for me, selecting any command module and then attempting to add a MK16 parachute produces a crash immediately upon selecting the parachute from the parts list. My ksp log doesn't show anything of interest but Player.log has the following entry multiple times at the end of the file:

NullReferenceException: Object reference not set to an instance of an object
  at ModuleParachute.SetConvectiveStats () [0x00000] in <filename unknown>:0 
  at ModuleParachute.FixedUpdate () [0x00000] in <filename unknown>:0 

(Filename:  Line: -1)

This isn't the only sequence of events that leads to a crash but it is an easy one to replicate.

Edited September 2, 2015 by SatanSoldier

[sal_vager]

Hi SatanSoldier, can you please put the full Player.log after one of these crashes on a file or paste site for us.

You can find it in /home/user/.config/unity3d/Squad/Kerbal Space Program/

Also please test a new career or sandbox game.

[SatanSoldier]

Player.log

Part One

Part Two

New games in multiple game modes produce the same crash.

[sal_vager]

There's no obvious cause here so you're going to have to test a few things.

First, verify your game files in Steam, to make sure any corrupt or missing files are replaced.

If that doesn't solve it, test the KSP.x86 and then the KSP.x86_64 in the game folder directly, this removes any interference from Steam and also any issue with starting KSP remotely (desktop shortcut).

If it still crashes, try uninstalling the Catalyst/FGLRX driver, rebooting and running KSP with the built-in xorg Radeon driver.

[Claw]

This is a known issue for some Linux users. (It's actually a problem in windows too, but only log spams and doesn't crash.) There is no stock fix or workaround for this right now, except the obvious "don't use parachutes."

You might be able to flush this out by launching a craft without a parachute, then revert to the editor and add one on. I doubt this will work, but I don't have linux to verify.

If you aren't opposed to add-ons, you can download my StockBugFix add-on which fixes this issue. Specifically, you are looking for ModuleParachuteFix.

http://forum.kerbalspaceprogram.com/threads/97285

Cheers,

-Claw

[SatanSoldier]

There's no obvious cause here so you're going to have to test a few things.

First, verify your game files in Steam, to make sure any corrupt or missing files are replaced.

If that doesn't solve it, test the KSP.x86 and then the KSP.x86_64 in the game folder directly, this removes any interference from Steam and also any issue with starting KSP remotely (desktop shortcut).

If it still crashes, try uninstalling the Catalyst/FGLRX driver, rebooting and running KSP with the built-in xorg Radeon driver.

Well, that's interesting. The x86_64 executable doesn't seem to produce the crash. I guess I'll just stick to using the 64bit version, though I thought that was supposed to be the less stable one.

[sal_vager]

That actually suggests you're missing a 32bit library, I noticed you're on a 64bit version of Linux so it'll have 64bit versions of the libraries that KSP needs installed, rather than 32bit versions.

If you open a terminal in the KSP folder and use this line;

ldd KSP.x86 | grep "not found"

It'll say if anything's missing, but will also detect the 64bit versions of some things.

Your log listed fglrx in the stack trace, so most likely you're missing the 32bit version of mesa, some parts of which are still needed by 32bit KSP.

If you run this line in a terminal;

sudo apt-get install libgl1-mesa-glx:i386

It'll install the bits you need so KSP.x86 will work.

Or just stick to KSP.x86_64 which you can make Steam open for you by adding this;

%command%_64

To the Steam launch options for KSP.

Edited September 2, 2015 by sal_vager

[Claw]

Well, that's interesting. The x86_64 executable doesn't seem to produce the crash.

In that case, it it still producing the errors (but no crash)? You can open the debug dialogue to watch (MOD+F12).

Also, sal is much more the expert on Linux, so there might be more to it. I just know this bug has hit other Linux users and also shows up in Windows. It's just that the windows error doesn't cause a crash, and the error often stops (for that craft) after launch and revert. But the 32 vs 64-bit thing at least explains to me why it's only some folks.

Cheers,

-Claw

Edited September 2, 2015 by Claw

[SatanSoldier]

That actually suggests you're missing a 32bit library, I noticed you're on a 64bit version of Linux so it'll have 64bit versions of the libraries that KSP needs installed, rather than 32bit versions.

If you open a terminal in the KSP folder and use this line;

ldd KSP.x86 | grep "not found"

It'll say if anything's missing, but will also detect the 64bit versions of some things.

Your log listed fglrx in the stack trace, so most likely you're missing the 32bit version of mesa, some parts of which are still needed by 32bit KSP.

If you run this line in a terminal;

sudo apt-get install libgl1-mesa-glx:i386

It'll install the bits you need so KSP.x86 will work.

Or just stick to KSP.x86_64 which you can make Steam open for you by adding this;

%command%_64

To the Steam launch options for KSP.

ldd reported nothing, and apt-get says that library is already installed. I'll stick to x64, so thank you for the launch option switch, that was my next question.

At this point I will consider this resolved, thank you both for your assistance.

Edited September 2, 2015 by SatanSoldier