LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Crash LV2013

Run this VI 3 times, at the 3rd time, LV crashes.

run , run , run=crash

 

Can anyone confirm this behavior?

 

 

SR1.png

 

0 Kudos
Message 1 of 5
(2,715 Views)

Please, can anyone confirm this behavior?

 

Run this VI 3 times, at the 3rd time, LV crashes.

 

 

(1) run

(2) run

(3) run=crash

 

(LV2011, LV2012 or LV2013)

 

Thank you very much to all.   Smiley Happy

 

 

 

0 Kudos
Message 2 of 5
(2,684 Views)

I can confirm the crash, what are you trying to do with that VI?

 

Thanks,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

Message 3 of 5
(2,673 Views)

The code appears to want to move the contents of another BD onto This BD (that Move invoke node should be producing an error since ThisVI is running)

 

Since owner is not the same object as source the T Constant is (Should be) ignored  Replacing it with F or deleting it causes a crash every time!

 

Honestly, this looks like someone forgot to protect us from ourselves.  Moving objects to the BD of a vi that is not idle is completely wrong.   You just cannot do that! (In Theory it might be possible to add objects to a BD inside a disable structure since that could not possibly be reached and should be excluded from the code section of the vi BUT --- that isn't how I understand the compiler works.)

 

You probably found a edge case where NI forgot to check for "Insane Object between Monitor and Chair."


"Should be" isn't "Is" -Jay
Message 4 of 5
(2,662 Views)

Jeff-P : what are you trying to do with that VI?

 

sorry, my English is not good enough to explain what I tried to do.  Smiley Frustrated

 

(some tests to try to solve a problem in my code SubVI from XNode (ReplaceSelf)

 

 

Jeff·Þ·Bohrer :

 

thank you very much for your explanations.

 

You probably found a edge case where NI forgot to check for "Insane Object between Monitor and Chair."

 

CAR 441160

0 Kudos
Message 5 of 5
(2,647 Views)