1.0.4 Parachutes throwing exceptions

[tutike2000]

Edit: Claw's Parachute stock bugfix seems to fix this error. Get it here: http://forum.kerbalspaceprogram.com/threads/97285-KSP-v1-0-4-Stock-Bug-Fix-Modules-%28Release-v1-0-4a-1-1-Jul-15%29

-----------

I keep getting this exception:

[EXC 21:12:12.587] NullReferenceException: Object reference not set to an instance of an object

ModuleParachute.SetConvectiveStats ()

ModuleParachute.FixedUpdate ()

My steps to reproduce:

- Deleted entire game folder

- Re-downloaded 1.0.4 via Steam

- Start new game, Sandbox, default settings

- Click the VAB

- Add mk-1 command pod (any part will do, I believe)

- Pick up a chute (any of the 3 'normal' chutes will trigger the exceptions)

- Alt-F12, Debug: Hundreds of exceptions are being thrown

- Attach 10 parachutes to your pod, framerate drops considerably

Edited July 3, 2015 by tutike2000

[KerbalEssences]

You came like a minute before me I have exactly the same issue. Seriously check my post.. the similarities!

[sal_vager]

If you could post a bug tracker issue for this that'd be great, reproduced here on Linux as well.

[TheSoundOfTrees]

Probably related : Linux, Steam version. Selecting a parachute (any kind) in the VAB parts causes immediate crash to desktop (no crash.log generated, it seems)

[sal_vager]

What's in your KSP.log and player.log TheSoundOfTrees?

[TheSoundOfTrees]

Relevant parts seem to be (I'll upload the files somewhere if needed) :

player.log :

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)

in KSP.log, same thing except with less information.

There is also the following in player.log, just after switching to the VAB :

The referenced script on this Behaviour is missing!

(Filename: Line: 1771)

Not sure if it helps - will post links as soon as I understand how to upload and do it

the player.log file

Edited June 23, 2015 by TheSoundOfTrees

[tutike2000]

If you could post a bug tracker issue for this that'd be great, reproduced here on Linux as well.

I've registered and signed in, but I don't see a 'New Issue' button anywhere.

- - - Updated - - -

Here's my ksp.log https://dl.dropboxusercontent.com/u/15458284/1.0.4.ChuteBug/KSP.log

and my dxdiag https://dl.dropboxusercontent.com/u/15458284/1.0.4.ChuteBug/DxDiag.txt

[troyfawkes]

I have this exact same issue. Not sure what the effects are but my log is having a lot of fun.

[tutike2000]

I have this exact same issue. Not sure what the effects are but my log is having a lot of fun.

Exceptions in large numbers will eat up lots of CPU cycles.

Try putting 20 chutes on a craft. you should definitely feel the FPS drop then.

[TheSoundOfTrees]

After more tests, it seems it is an issue with Steam : if I launch the game from the directory, the game doesn't crash when I select a parachute in VAB.

[stevehead]

Same problem here with the exceptions being thrown. I first noticed with a modded install I was updating from 1.0.2, then I tried an unmodded clean install of 1.0.4 from Steam (i.e. I delete the Steam KSP folder, then reinstall) and the same thing was occurring. I do not launch from Steam, I launch directly from the folder, which is not the original Steam install but a copy stored elsewhere on my computer. Good thing I didn't upgrade my main playthrough install yet since I'm not trusting 1.0.3/1.0.4... guess I'm sticking with 1.0.2 for the time being .

By the way, I'm not having actual crashes, just the exception spam in the log.

[tutike2000]

By the way, I'm not having actual crashes, just the exception spam in the log.

Yeah, same. Doesn't matter how I start the game. (Although I do have Steam Overlay disabled)

[-ELF-]

On the same boat here. Linux Mint 32bit, mods - KER, Claw's stock bugfixes.

Whenever I select the parachute in VAB or SPH, game crashes, and in the log a lot of:

NullReferenceException: Object reference not set to an instance of an object

ModuleParachute.SetConvectiveStats ()

ModuleParachute.FixedUpdate ()

[LittleBlueGaming]

Confirmed log spam here as well. Doesn't crash, but does seem to affect performance in the VAB.

[Andymeows]

Confirmed crashing on 64-bit Linux Mint. The window closes as soon as I select any parachute.

1) Deleted game content from Steam and reinstalled

2) Start (or resume) new sandbox game

3) Enter VAB

4) Select MK1 Command Pod

5) Click Utility, then second page.

6) Click M16, MK12-R, or M16-XL parachute.

7) ~0.5 seconds later the window closes.

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

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

Loading crafts that already have a parachute work just fine. Even clicking the parachute to detach it, and leaving it in the editor area is fine.

Please let me know if I can provide anything else.

[-ELF-]

Andymeows, I provided your info on the bugtracker, thank you for files.

Bug is confirmed, but there are some speculations on severity, because it is not reproduced on testing PCs, as long as I understand.

I will try to keep this thread updated with progress on the bug.

You can read it yourself here:

http://bugs.kerbalspaceprogram.com/issues/5169

[Squelch]

Can someone please confirm this is Linux Mint and Steam specific?

Ksp can be run directly from the installed folder and will bypass Steam client which has its own crash handler. I'm particularly interested in finding reports of this on other distros and a stack trace of the event so we can narrow it down. Please direct your info to the tracker too where it can be dealt with.

Parachutes cause NullReferenceExceptions in VAB

Your efforts on this issue are most appreciated. Thanks.

[-ELF-]

This happens to me on Linux Mint x86, distro from KSP store, not from Steam, launched via KSP.x86 directly from KSP folder.

[sal_vager]

It might help to know that the Steam overlay is 32bit only and breaks on Linux x64, there is no 64bit version of that Steam library yet, and you can't run LD on a lib to see what it needs.

Edit:

Oh and I get the nullrefs but not the crash, Xubuntu 15.04 with Nvidia 346.

Edited June 26, 2015 by sal_vager

[Squelch]

;2042809']This happens to me on Linux Mint x86' date=' distro from KSP store, not from Steam, launched via KSP.x86 directly from KSP folder.[/quote']

That's interesting thank you.

It might help to know that the Steam overlay is 32bit only and breaks on Linux x64, there is no 64bit version of that Steam library yet, and you can't run LD on a lib to see what it needs.

Edit:

Oh and I get the nullrefs but not the crash, Xubuntu 15.04 with Nvidia 346.

Yes, I have observed the same on the same distro and version, so this tentatively rules out Steam and its overlay. It looks like the crash is unique to Mint at the moment, and is possibly a library mismatch.

ELF, could you please navigate to the KSP install folder, open a terminal, and run the following:

sudo ldd ./KSP.x86 > ksp-deps.txt

and attach the outputted text file here and/or on the issue? This will list the library dependencies and versions for KSP available on your system, and we can compare to other distributions to find a potential mismatch.

Edit to note. The NRE issue has probably been isolated, but the crash is something that we don't really want lurking around to come and bite at another time. If we can identify or mitigate it, that's one less thing to worry about.

Edited June 26, 2015 by Squelch
case

[-ELF-]

Sure thing, Squelch!

Here is the text from ksp-deps.txt by ldd on ./KSP.x86:

linux-gate.so.1 => (0xb7779000)

libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb7755000)

libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb7739000)

librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb772f000)

libGLU.so.1 => /usr/lib/i386-linux-gnu/libGLU.so.1 (0xb76bc000)

libGL.so.1 => /usr/lib/libGL.so.1 (0xb7614000)

libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xb74e0000)

libXcursor.so.1 => /usr/lib/i386-linux-gnu/libXcursor.so.1 (0xb74d5000)

libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb73eb000)

libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb73a5000)

libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb7388000)

libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb71da000)

/lib/ld-linux.so.2 (0xb777a000)

libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xb71c7000)

libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xb71a4000)

libXrender.so.1 => /usr/lib/i386-linux-gnu/libXrender.so.1 (0xb7199000)

libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xb7193000)

libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xb718f000)

libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xb7188000)

I will attach the file to the bug on Redmine.

UPD:

Priority of bug was raised to high on bugtracker.

Edited June 26, 2015 by [ELF]
bug information update

[troyfawkes]

Can someone please confirm this is Linux Mint and Steam specific?

Just wanted to clarify that the crash might be Linux specific but the bug/log spam is also on Windows (I get it on Windows 7).

[Chrozayis]

I have been getting VAB related crashes in mint specifically with this ship

https://drive.google.com/file/d/0B-k...ew?usp=sharing

here is the ksp-deps contents if that helps

linux-gate.so.1 => (0xf7774000)

libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf774c000)

libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf7730000)

librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf7726000)

libGLU.so.1 => /usr/lib/i386-linux-gnu/libGLU.so.1 (0xf76b3000)

libGL.so.1 => /usr/lib/i386-linux-gnu/mesa/libGL.so.1 (0xf7653000)

libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf751f000)

libXcursor.so.1 => /usr/lib/i386-linux-gnu/libXcursor.so.1 (0xf7514000)

libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf742a000)

libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf73e4000)

libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf73c7000)

libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7219000)

/lib/ld-linux.so.2 (0xf7775000)

libglapi.so.0 => /usr/lib/i386-linux-gnu/libglapi.so.0 (0xf7201000)

libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf71ed000)

libXdamage.so.1 => /usr/lib/i386-linux-gnu/libXdamage.so.1 (0xf71e9000)

libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xf71e3000)

libX11-xcb.so.1 => /usr/lib/i386-linux-gnu/libX11-xcb.so.1 (0xf71e0000)

libxcb-glx.so.0 => /usr/lib/i386-linux-gnu/libxcb-glx.so.0 (0xf71c8000)

libxcb-dri2.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri2.so.0 (0xf71c1000)

libxcb-dri3.so.0 => /usr/lib/i386-linux-gnu/libxcb-dri3.so.0 (0xf71bd000)

libxcb-present.so.0 => /usr/lib/i386-linux-gnu/libxcb-present.so.0 (0xf71b9000)

libxcb-sync.so.1 => /usr/lib/i386-linux-gnu/libxcb-sync.so.1 (0xf71b2000)

libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf7190000)

libxshmfence.so.1 => /usr/lib/i386-linux-gnu/libxshmfence.so.1 (0xf718c000)

libXxf86vm.so.1 => /usr/lib/i386-linux-gnu/libXxf86vm.so.1 (0xf7186000)

libdrm.so.2 => /usr/lib/i386-linux-gnu/libdrm.so.2 (0xf7178000)

libXrender.so.1 => /usr/lib/i386-linux-gnu/libXrender.so.1 (0xf716d000)

libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf7168000)

libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf7161000)

[shjohnson.pi]

I'm having crashes as well, see http://forum.kerbalspaceprogram.com/threads/126847-1-0-4-CTD-Training-Scenarios

I was told to add my libraries here also, but I'm running Ubuntu Unity, not Mint.

linux-gate.so.1 => (0xf77a7000)

libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf777c000)

libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf775f000)

librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf7755000)

libGLU.so.1 => /usr/lib/i386-linux-gnu/libGLU.so.1 (0xf76e2000)

libGL.so.1 => /usr/lib32/fglrx/libGL.so.1 (0xf7637000)

libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf74ec000)

libXcursor.so.1 => /usr/lib/i386-linux-gnu/libXcursor.so.1 (0xf74e1000)

libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf73eb000)

libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf739e000)

libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf7381000)

libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf71c6000)

/lib/ld-linux.so.2 (0xf77a8000)

libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xf71b1000)

libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf718e000)

libXrender.so.1 => /usr/lib/i386-linux-gnu/libXrender.so.1 (0xf7182000)

libXfixes.so.3 => /usr/lib/i386-linux-gnu/libXfixes.so.3 (0xf717b000)

libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf7177000)

libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf7170000)

[smjjames]

Massive logspam confirmed for Windows 7, 64x.

SQUAD, how in the heck did you guys miss this one??? lol........ I mean, seriously, you and your testers DO have something like exception detector that shows when something is spamming errors, right?

Edit: Just to be clear, I'm not bashing SQUAD or anything, just really surprised that an errorspam problem got through testing. That kind of errorspam is normally something that I would expect from a mod, honestly.

Edit2: Got curious and tried to use a mod chute (still uses the same chute module as stock) and the exceptions still occur. Granted though, the ones I was looking at haven't updated to 1.0.4 yet.

I wonder if the problem is because theres some line that the game is expecting, but isn't there.

Edited June 27, 2015 by smjjames