Application slows down after a couple weeks use

[scott.williams]

We have an application running in production, and they say that about every 2 weeks it starts to slow down. They just re-boot the PC and it is running fast again. Are there any known internal files that may accumulate data using Windows XP with Labview 6.1, and therefore slow down the PC?

[BJD1613]

Are you using any references in your application? If so you might want to make sure they are being used properly. They could lead to a memory leak which in turn could be slowing down your application.

[chutla]

Greetings, Scott:

Something here smells like a memory leak, which can arrive from a multitude of sources, least likely of which being your Labview application. First you want to look at your available memory right after you start the program, and then again after a couple of weeks, to verify that it really is a memory problem...all my bets are on this, however.
The safest bet is to start Windows in the selective startup mode (you can use 'msconfig' at a command prompt to access this). This will make windows fire up with the minimal necessary processes running. (I'm assuming, of course, that your Labview program is the only really important application running on that particular machine:) ) Give this a try, take two aspirin, and call me in the morning!


Good luck!

Eric

[Milchbilch]

Hello there,

I experienced the same problem in a DAQ application where data was
shown in a simple chart. After one day running the vi was slower than
when I started it.

I think that this was due to the fact that I just added the new data
point to the chart without removing the oldest one at the same time.
So the "data array" of the chart got bigger and bigger (the history
length does - as I think - not limit the number of data points saved
but only the number that is displayed.)

Perhaps there is something like that in your vi, too?