Program crash when using the decoupler

[kennyj]

KSP Version: v0.90.0.0 Beta Linux 64-bit (Ubuntu 14.04.1 LTS)

What Happens: Program crashes with core dump when decouplers in a certain condition

Mods / Add-Ons: All Stock

Steps to replicate:

1) Load craft

2) Launch craft

3) Right click on decoupler and choose decouple. Alt. use staging to decouple.

Result:

Program crashes with core dump.

Notes:

TR-2V, TR-2C and TR-18D tested

Seems like using some other element below the decoupler can be a workaround.

Craft file:

https://mega.co.nz/#!B5hE1IiR!oHygmgGMgETZb-QDMuh1uILlrn2ybDtDViWKGelMdwU

[sal_vager]

Yep you've got a bugged craft here, I get a stack trace as well, but only with your craft, I have no idea how you managed to break this but I think you're going to have to rebuild that craft from scratch.

This is what I get:

Stacktrace:

  at (wrapper managed-to-native) UnityEngine.Object.CompareBaseObjectsInternal (UnityEngine.Object,UnityEngine.Object) <0x00060>
  at (wrapper managed-to-native) UnityEngine.Object.CompareBaseObjectsInternal (UnityEngine.Object,UnityEngine.Object) <0x00060>
  at UnityEngine.Object.CompareBaseObjects (UnityEngine.Object,UnityEngine.Object) <0x00017>
  at UnityEngine.Object.op_Equality (UnityEngine.Object,UnityEngine.Object) <0x00017>
  at Part.FindPartThroughNodes (Part,Part) <0x00037>
(Removed 1000 lines identical to the above)
  at Part.PromoteToPhysicalPart () <0x0052b>
  at Part.decouple (single) <0x0003f>
  at ModuleDecouple.OnDecouple () <0x0068f>
  at ModuleDecouple.OnActive () <0x0002f>
  at Part.ModulesOnActivate () <0x0003e>
  at Part.activate (int,Vessel) <0x001b3>
  at Staging.activateStage (int) <0x00233>
  at Staging.activateNextStage () <0x0001f>
  at Staging.ActivateNextStage () <0x0001b>
  at FlightInputHandler.Update () <0x005cb>
  at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0x00059>

Native stacktrace:

	/home/user/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/libmono.so(+0x931f8) [0x7ff773b731f8]
	/home/user/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/libmono.so(+0xd0c19) [0x7ff773bb0c19]
	/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7ff77e048340]
	./KSP.x86_64() [0x7f316c]
	./KSP.x86_64() [0xccbf59]
	[0x406733f0]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

[GarrettKajmowicz]

I've run into something similar with the TR-2C stack separator as well. I'm running x86_64 linux. Unlike the parent, my install is modded with some common mods.

My game file is here:

https://infotomb.com/sw4hy.txt

The KSP.log file is uninteresting. It records me completing a contract, and getting rewarded. The log file ends with:

[LOG 21:43:16.450] Contract (Science data from space around Moho.): We've just received experimental data from space around Moho! Good work.

<b><#8BED8B>Completion Rewards:</></>

<#B4D455>£229,395 <#caff00>(+2,280)</> </>

<#6DCFF6>©7 </>

<#E0D503>¡700 <#feb200>(-300)</> </>

[LOG 21:43:28.126] [PlanetariumCamera]: Focus: Moho Scanner

[LOG 21:43:28.130] Maneuver Mode enabled

[LOG 21:43:38.790] Camera Mode: AUTO

[LOG 21:44:05.382] Flight State Captured

[LOG 21:44:05.392] Saving Achievements Tree...

[LOG 21:44:05.392] Saving Achievements Tree...

[LOG 21:44:05.392] Saving Achievements Tree...

[LOG 21:44:05.392] Saving Achievements Tree...

[LOG 21:44:05.392] Saving Achievements Tree...

[LOG 21:44:05.393] Saving Achievements Tree...

This occurs right about the point at which the game crashes.

A few things to note - this is a craft with 2 probe cores on it being cleaved in two (basically a rover plus a satelite). I've had nearly the same thing happen in the past with a rover body on the Mun which I was trying to cleave with the TR-2C from its landing rocket - repeated crash.

What other information would be useful to debug this?

Edited April 9, 2015 by GarrettKajmowicz
Replace with URL which will last longer.