LabVIEW IPE Structure Unbundle/Bundle Type Propagation Error/Crash

[Jim_Kring]

SRN 03988339
LabVIEW 2025 Q3 f2

LabVIEW crashes when wiring a bundled cluster of elements to an IPE structure's unbundle/bundle nodes when (a) there is wire internally connecting the unbundle to the bundle, (b) the outer terminal of the IPE structure's unbundle is unwired, and (c) a wire from a bundle with a cluster of elements is connected to the outer terminal of the IPE structure's unbundle.

The work-around (lesson) is: do not pre-wire the internal unbundle/bundle until after you wire the external unbundle input to the IPE structure.

See attached IPE_Crash_Reproducer.zip file for Example VI (configured as shown, below, in Before the Crash)

Before the Crash

Triggering the Crash

[wiebe@CARYA]

Reproduced in:

LV24.3.2f2, 64-bit.

LV24.1.1f1, 32-bit.

LV18 64-bit.

So probably a problem in every released version...

[BertMcMahan]

Reproduced in 2023 Q3 64-bit, 23.3.6f6. Made the diagram from scratch, so your VI isn't unusually corrupted somehow.

[wiebe@CARYA]

---

@BertMcMahan wrote:

Reproduced in 2023 Q3 64-bit, 23.3.6f6. Made the diagram from scratch, so your VI isn't unusually corrupted somehow.

---

I also made all the VIs from scratch.

I used an error cluster, the items have labels and so does the cluster, so that saves a few clicks. Works well (as in: it still crashes).

[billko]

That's a very specific workflow. Did you find it by accident?

That was the dumbest question I have asked so far. I guess if it was part of your workflow you would've seen it years ago.

[Jim_Kring]

---

@billko wrote:

That's a very specific workflow. Did you find it by accident?

That was the dumbest question I have asked so far. I guess if it was part of your workflow you would've seen it years ago.

---

I happened upon it while trying to insert an IPE Structure directly inline with an existing cluster wire inside a state machine. This has a lot of repetitive steps so my mind is always playing with how to reduce steps and maybe automate them, plus curious about how the different parts behave.

once I experienced the crash, I whittled things down to the simplest way to reproduce it, to make it very easy to verify it’s really a bug (by support engineers) and also easy to start working on a fix (by R&D).

That’s why it looks specific: because all that’s left is (hopefully) the specific causes of the bug.

My guess is that it’s some corner case having to do with the order of operations in edit-time type propagation and the smartness around how untyped named bundlers bind to elements when a datatype is first assigned. There’s a lot of smarts and magic behind the type propagation in LabVIEW.

cheers

[Jim_Kring · Accepted solution]

Bug ID: 3403173