LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I keep a vi (built with LV 8.0.1) from consuming so much memory over time, resulting in the Blue screen of death?

I am having a tough time from keeping this vi I made from consuming so much memory over time.  I made it using LV 8.0.1.  Basically, all it is doing is reading in analog input line from a usb device linked to a sensor that basically monitors the line.  Whenever the sensor goes on, the count increments by one no matter how long the signal is held on for and then the time and count of this event is then written to a data log lvm file.  This occurs each time the sensor goes on.  Which is why I am uncertain as to why it still consumes memory other than when it first goes high and writes to the data log.  I didn't think it would keep using the memory up if the sensor was off.  I was wondering if anybody has any suggestions on keeping a simple vi like this from consuming so much memory.  Basically, if running for more than a 1/2 hour, the smaller computer gets a memory dump crash (blue screen with some kind of a reference to nimxdfk.dll).  I was unable to see any refnums that needed to be closed within the while loops.  Am I supposed to clear the task after each iteration?  A little confused.  It is fully commented on if you have the time to look it over.  Thank you very much for your suggestions.
 

Message Edited by scott_7723 on 02-08-2007 01:30 PM

0 Kudos
Message 1 of 3
(2,974 Views)
Hi Scott, I suggest you to repost this question in the LabVIEW forum: this one is related to CVI only! Smiley Wink


Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
Message 2 of 3
(2,960 Views)
You know, I think that would be a good idea.  Don't know how I managed that one.  Thanks; sorry bout that
0 Kudos
Message 3 of 3
(2,945 Views)