I am getting said runtime error after about 15 minutes of having my vi open. This error occurs whether I am simulating the vi or editing it. Originally, I had no such problems, but after many modifications and additions, I encountered this problem. The program operates normally, but after 15 minutes, i hear my HDD start to go crazy and then within a minute everything is crawling. It takes 15 minutes just to close all the programs and open windows. I originally thought it might be a bad reference, but the problem also occured when I hadn't been simulating, and I couldn't find any bad references. This particular vi is nearly impossible to debug because it is a vi that was included with the DAQ from Omega that I purchased. I made some modifications, but nothing to in depth (mainly isolating individual columns in an array and saving them to seperate files). The original vi is quite large, with many sub vi's, but again this problem happened after making changes to the parent vi and can occur when not in simulation mode. I have already tried reinstalling labview. I am hoping this is a common occurrence that can be narrowed down to make it easier to debug. Any help is appreciated.

ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

I figured out that my strange error is invoked by calling TDMS primitives with an invalid refnum. (go look there, NI)

Of course this should yield a simple error in the code, not a pop-up and crash.

Message 11 of 13

(1,390 Views)

BTW. The error also reproduces in an executable.

Message 12 of 13

(1,387 Views)

This is filed as CAR #128520. It will be fixed in the very next LabVIEW release.

Sorry for the inconvenience,

Herbert

Message 13 of 13

(1,358 Views)