LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Crash LabVIEW with VI Property Node

If you have a new VI that's never been saved (i.e. path is "Not a Path"), then this can cause LabVIEW to crash:

paul_cardinale_0-1704236856183.png

 

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 1 of 6
(758 Views)

I could not reproduce the crash in the latest 2023 Q3

 

2024-01-02 19_27_06-Untitled 1 Front Panel _.png

0 Kudos
Message 2 of 6
(738 Views)

@Lavezza wrote:

I could not reproduce the crash in the latest 2023 Q3

 

2024-01-02 19_27_06-Untitled 1 Front Panel _.png


When an output of a property node is not wired, the code that would get the value is skipped.

Try wiring the output "Library" to something.

0 Kudos
Message 3 of 6
(723 Views)

@paul_a_cardinale wrote:


When an output of a property node is not wired, the code that would get the value is skipped.


Duh. Of course. 🙄

 

But it still doesn't crash for me.

2024-01-02 20_25_49-Explain Error.png

0 Kudos
Message 4 of 6
(711 Views)

No crash in 2021 either. That's the only two versions I have available right now.

 

2024-01-02 21_04_36-Untitled 1 Front Panel _.png

0 Kudos
Message 5 of 6
(700 Views)

The problem is occurring in a VI that's being called by the configuration VI of an Express VI.

Outside of that circumstance, I also cannot recreate the problem.

The VI that's trying to get the library reference is in context "NI.LV.Express".  The VI that's being referred to is in context "My Computer".  (But when I make test code that uses those contexts, I still don't get a crash.  (For some reason, it only happens when an Express VI's configuration is running.)

I observe the problem in LV 2019, 2020, & 2021.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 6 of 6
(643 Views)