Bug related to EVA construction mode

[Sparffles]

Hello,

I've found an issue where I can reliably produce a NullReferenceException that results in an unresponsive clone of a Kerbal stuck on a ladder. I'd like to find out if this is a well known issue since the bug reporting process seems to be pretty involved, and I am pretty lazy. To produce the bug:

1) Have two craft with docking ports near each other in space, one with an engineer on board. This can be accomplished by decoupling a craft from your space station, for example

2) With the craft carrying the engineer, target the docking port of the second craft (So that the pink markers appear on your nav-ball).

3) EVA your engineer and use the EVA construction mode to remove the docking port of the second craft that you targeted in step (2).

4) Board the engineer onto his/her original craft. The engineer should now be present inside the craft, but a clone will be stuck on the ladder outside.

I have the base game installed, no mods, version 1.12.2.3167 (WindowsPlayer x64) en-us.

From the log:
[LOG 03:43:34.572] [FLIGHT GLOBALS]: Switching To Vessel Bill Kerman ----------------------
[LOG 03:43:34.575] [PlanetariumCamera]: Focus: Bill Kerman
[LOG 03:43:34.601] [ApplicationLauncher] SetVisible:
[LOG 03:43:34.602] [ApplicationLauncher] SetHidden:
[LOG 03:43:40.479] Event Weld Started not assigned to state Ladder (Idle)
[LOG 03:43:46.196] Event Weld Started not assigned to state Ladder (Idle)
[LOG 03:43:50.277] Event Weld Started not assigned to state Ladder (Idle)
[LOG 03:44:04.682] [FLIGHT GLOBALS]: Switching To Vessel Station Beta ----------------------
[LOG 03:44:04.683] [PlanetariumCamera]: Focus: Station Beta
[LOG 03:44:04.697] Camera Mode: AUTO
[EXC 03:44:04.723] NullReferenceException: Object reference not set to an instance of an object
    ProtoTargetInfo..ctor (ITargetable tgt) (at <cd473063d3a2482f8d93d388d0c95035>:0)
    Vessel.ResumeTarget () (at <cd473063d3a2482f8d93d388d0c95035>:0)
    Vessel.MakeActive () (at <cd473063d3a2482f8d93d388d0c95035>:0)
    FlightGlobals.setActiveVessel (Vessel v, System.Boolean force, System.Boolean clearDeadVessels) (at <cd473063d3a2482f8d93d388d0c95035>:0)
    FlightGlobals.ForceSetActiveVessel (Vessel v) (at <cd473063d3a2482f8d93d388d0c95035>:0)
    KerbalEVA.proceedAndBoard (Part p) (at <cd473063d3a2482f8d93d388d0c95035>:0)
    KerbalEVA.BoardPart (Part p) (at <cd473063d3a2482f8d93d388d0c95035>:0)
    KerbalEVA.<SetupFSM>b__424_53 () (at <cd473063d3a2482f8d93d388d0c95035>:0)
    KerbalFSM.RunEvent (KFSMEvent evt) (at <cd473063d3a2482f8d93d388d0c95035>:0)
    KerbalFSM.updateFSM (KFSMUpdateMode mode) (at <cd473063d3a2482f8d93d388d0c95035>:0)
    KerbalFSM.UpdateFSM () (at <cd473063d3a2482f8d93d388d0c95035>:0)
    KerbalEVA.Update () (at <cd473063d3a2482f8d93d388d0c95035>:0)

Edited October 3, 2021 by Sparffles

[Gargamel]

Moved to Tech Support. 

2 hours ago, Sparffles said:

I'd like to find out if this is a well known issue since the bug reporting process seems to be pretty involved, and I am pretty lazy.

It's actually quite simple.   I'd recommend trying.