EVA kerbal destroy throwing UnityEngine.Collider exceptions?

[SixHourDays]

This has started popping up whenever I board an eva Kerbal back into a ship...and I don't know why.

[EXC 20:56:06.040] InvalidOperationException: Collection was modified; enumeration operation may not execute.
    System.Collections.Generic.List`1+Enumerator[UnityEngine.Collider].VerifyState ()
    System.Collections.Generic.List`1+Enumerator[UnityEngine.Collider].MoveNext ()
    Part.OnDestroy ()

My only thought is that I've used Part::AddModule("myModuleName") on the kerbalEVA part.  I added three of my own PartModules that way - they're simple modules, nothing to do with collision, just messing with the PartModule::Events.

Is it saying that I've altered the collection of Colliders by adding PartModules?  That doesn't make any sense to me.

Has anyone seen such an error before on EVA kerbals boarding craft / otherwise being destroyed?

 

 

[Diazo]

Are you hooking into the .OnDestroy() event? That looks to be where the error is starting.

If yes, could you post your code for that?

If no, try removing your mods, it might be another mod causing the issue.

D.

[SixHourDays]

My PartModules don't implement OnDestroy.

I'm working off of KSP 1.04 (I'll upgrade when I've stabilized things), and it's completely stock, short of my mod.

I have one additional piece of info - it only happens if the Kerbal boards and they've got science on them.  Which...makes me sad cause it's probably my bug then (my mod deals in shoving around science).  Still, unsure how altering kerbal science would affect the collision stuff.

Edited December 31, 2015 by SixHourDays

[xEvilReeperx]

Looks like a bug in the stock logic (assuming 1.0.4's Part.OnDestroy is similar to the current version). Seems to be on the bug tracker already so nothing to be done except try and avoid causing it while testing

[SixHourDays]

Ahhhhh ok then!  <FeelsGood.gif>!  That's the second stock bug I've bumped into and thought was mine.  Thanks for the bug tracker link.