issues with labview and memory leaks

Hi, we have an issue with labview build applications and win2000 sp4. The computers where the two apps are working are controlled remotely from time to time, so the applications are not monitored. After some time, a day or two, one of the application (can be any of the two) starts consuming memory until the computer freezes. If a user starts controlling the computer and maximize and minimize the panel of the application the memory is instantly released and all comes back to normal. Also the memory leaks was observed with the DataSocked (cwdss.exe process) and the sollution is the same.Does anyone have any explanation of this?thankscosmininstronica s.r.l.

Do you have a loop where references are opened.  This could be for anything like openeing a reference to a file, a datasocket, an ActiveX class, etc..
If so, is the reference being closed?  Typically, you would want to open the reference before any loop, so that it is opened only once, and then closed after the loop when you no longer need it.
However, the above is only speculation because we would need to see your code to make any type of assessment.
R

I forgot to mention we use labview 8.5.1 (I will disregard the post from Joe)cosmin

I wouldn't disregard the post from Joe, from the info we have been given, that's about all of the conclusions we can come to.  We could google the exe, and see if there are reports of memory leaks, but you probably already did that.  So like Joe said, to determine why it is leaking, we need to see the context in which it is used.  Message Edited by drewsky on 08-06-2008 03:03 PM

Hi, the issue is about Labview 8.5.1. and win2000 and user interface. Memory leaks appears only if there is no user activity on the computer for a day or two. I maintained the applications from labview ver 6 to Labview 8.5.1. The problems began with 8.5.As I said in the original post, the same issue appear with DataSocket server on the same computers.The post is intended for NI guys, for a workaround until Labview 9 or I need to force the client to switch to XP.

Hi Cosmin, I have not heard of this issue before with other customers. - Can you please post your code so that I can test the issue itself?
- Is there a reason that you want to stick with Win 2000 and not move to Win XP?

Hi,
I can't post any code.
The problem is that a shift to XP is not easy because it's about critical control applications for this client and 6 computers that cannot be shut down like that. The situation is still ok because we use computer redundancy so if one fails is always another one that takes control. Also there are different applications from different supplier that I cannot be sure that will work well on XP (I can't take that risk).
I considered the shift to labview ver.8 but I need to recode some of the modifications made for ver. 8. 5. (the DSC part as we shift from the old tag engine that was running perfectly to shared variables).
One sollution was to create a new application that programaticaly maximize and minimize the front panel for the 3 labview built app that runs simultaneous on that computer but in critical situation when the user need to make some decisions that app can create problems.
It bugs me that the DataSocket server creates the same problems and also the fact that problems arises only on 4 out of 6 computers. The 2 computers that never had any problems are also with win2000 sp4 but there the app are the old versions from labview 7.1 (kept as comparison with the new apps).
 
cosmin

Hi I can remember a situation like this but in LabVIEW 7.1 a few years ago.I'm sorry I don't know the solution anymore but you can look on LAVA http://forums.lavag.org/home.htmland maybe find something.There should also be something like a call to the garbage cleaner (in LabVIEW) but instead of giving you a false linkI rather keep it to suggestions.In any case this is been sen before.

Since we can't look at your code I can only guess based on your clues.
Please review this <a href="http://zone.ni.com/devzone/cda/tut/p/id/7324#46630 2VO0SF00 by Category" target="_blank">known issue report </a>about datasockets leaking memory. The posted work-around is to open once use and then close.
Ben
BTW: THe LV 6 &gt;&gt;&gt; LV 8.5 DSC upgrade work is a real pain in the b$#% !

Hi Cosmin, Like Ben pointed out, it is a known issue in LabVIEW 8.5+. This begs the question, are you using ActiveX VIs to perform Datasocket opening and closing?