LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Running the VI causes LabVIEW to crash

Hello

 

While debugging a SW, I found that a particular VI, when run, causes LabVIEW to crash. This happens whether this VI is called while executing an exe or called by higher VI or even when it is run separately.

The VI to be run is NLD_Test_PP_Plot.vi present in the folder "Generic VI's".

The input for this VI is .csv file, which is attached. The csv file needs to be placed in a separate location and that path needs to be entered in the string constant in the VI.

 

Note: This VI is developed and run in LV v2009.

 

Thanks

Sharath

Download All
0 Kudos
Message 1 of 4
(3,033 Views)

LabVIEW did not crash for me (nor did it throw an error).  It made a bmp of your data and then exited.  I am using LV 2013.

 

Did it actually crash or did it throw an error?  If it crashed, do you have the crash zip file?

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 4
(3,017 Views)

I'm designing the VI using Labview2009.

I don't know about any crash file being generated but once I run the VI, all the opened VIs close after a couple of seconds.

This happens even in Highlight execution mode using breakpoints. No error throws up

 

0 Kudos
Message 3 of 4
(3,005 Views)

Hi, I tried to create a project, add the mentioned VI and Buit it with LV2012. Then I ran the VI (in debug) and it's built version at the same time and no crash, only an error message because I left the file path empty.

 

I had something similar with LV2012 that after I ran the built application while the project was still opened, the LV crashed. With a send crash report window.

 

But I guess the most reported bugs are adressed in each LV patch/version. You can expect LV2009 has some bugs, that are fixed by now (IMHO).

0 Kudos
Message 4 of 4
(2,983 Views)