Kerbal Space Program

Sorry, would like to point out, that for Linux it causes instant crash when you pick the parachute in VAB/SPH, So it is a game-breaker currently.
Probably it is possible to disable logging somehow, to step around it?
Also, guys on the forums reported that if you attach more chutes, it causes heavy lag on Windows also...

Can we have some sort of workaround meanwhile, please?

Part of my log listing the error itself and system stats.

Kerbal Space Program - 1.0.4.0 (LinuxPlayer)

OS: Linux 3.13 LinuxMint 17.1 32bit
CPU: AMD Athlon(tm) II X2 240 Processor (2)
RAM: 4007
GPU: AMD Radeon HD 7700 Series (729MB)
SM: 30 (OpenGL 4.4 [4.4.13372 Compatibility Profile Context 15.101.1001])
RT Formats: ARGB32, Depth, ARGBHalf, RGB565, ARGB4444, ARGB1555, Default, DefaultHDR, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8

[EXC 22:49:46.979] NullReferenceException: Object reference not set to an instance of an object
ModuleParachute.SetConvectiveStats ()
ModuleParachute.FixedUpdate ()

Could you please upload your logs including stacktrace from the crash as well as a craft that triggers it ELF? I am unable to invoke a crash under Win7 or Linux related to this issue yet, so I'm interested in the potential.

the only impact is log growth and no adverse game effects

I have to strongly disagree here. On Windows, having at least 5-6 chutes on a craft will lower my FPS from around 35 to around 10-15.
Try adding more and more chutes, eventually you will see your framerate become unplayable.

As requested additional info - this happens to me on 32 bit Linux Mint, distro from KSP Store, without Steam.
I launch KSP.x86 directly from KSP folder.

Edit:

As requested, I attach here a ksp-deps.txt file generated by ldd on KSP.x86 on my PC.

Hello, I was the one who originally submitted these logs and I can still actively reproduce the issue. Please let me know if there's anything else that I could provide that would be useful.

Player.log - http://pastebin.com/UwqrSVcn
KSP.log - http://pastebin.com/zbUcUJER

Can confirm game crash on Linux Ubuntu 14.04 64bit for Steam version.

Summary¶

It would appear that the log error spam attributed to this issue can cause crashes on some Linux platforms. There does not seem to be a definitive cause of the crash and no apparent library differences. Furthermore, the crashes do not seem to be restricted to one particular distribution.

Parachutes crashing the game also happening to me on Slackware 14.0 64-bit.

I am seeing other Unity-based games recently apply updates and start crashing reliably. Looks like all the branches of Unity were updated. Wild guess, but I wonder if this is a Unity bug somehow.

The cause of the parachute log spam has been identified, and is now in the process of being fixed.

The crashes on Linux platforms are a secondary symptom and now need emphasis, so rather than confuse this issue further, could someone please open a new issue that deals with the Linux crash under these circumstances specifically? It would be very helpful if any logs, stack traces or core dumps that are related to this problem can be attached.

...wow! While building my 13pax dual landing (Mun/Minmus) shuttle for tourists, I got two low drive space warnings (with an automatic Disk Cleanup between) and an impressive 62,909kB KSP.log file full of this scuttlebutt. I didn't run it all the way to getting a file pointer exception so I don't know if this bug can cause a crash in Win32. I'm going to keep the file for at least a couple of days if anyone's interested. (I'd have to Google Drive it or something.)

featherwinglove wrote:

I didn't run it all the way to getting a file pointer exception so I don't know if this bug can cause a crash in Win32. I'm going to keep the file for at least a couple of days if anyone's interested. (I'd have to Google Drive it or something.)

Thanks.

The log file can grow to very large sizes on Windows, and despite the system slowdown, crashes due to the parachute bug haven't been seen. We do know the nature of the error, and the cause, and it has been forwarded to the devs for attention. There is no need to keep your logs for this one.

In the meantime, there is a community fix/workaround that avoids the log spam and related issues, and can be found on the forums. However, we politely request that before reporting other issues, the fix is removed and the issue verified as reproducible in a stock game.

For me, at least, if multiple parachutes are added, the editor becomes unresponsive, even when input locks are released.