Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: issues with labview and memory leaks
1 view
Skip to first unread message
JoeLabView
Aug 6, 2008, 8:40:06 AM8/6/08
to
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
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
Karunya_R
Aug 7, 2008, 6:10:08 PM8/7/08
to
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?
- Is there a reason that you want to stick with Win 2000 and not move to Win XP?
cosmin
Aug 8, 2008, 4:10:06 AM8/8/08
to
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
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
Ben
Aug 8, 2008, 9:10:08 AM8/8/08
to
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 >>> LV 8.5 DSC upgrade work is a real pain in the b$#% !
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 >>> LV 8.5 DSC upgrade work is a real pain in the b$#% !
cosmin
Aug 12, 2008, 4:10:06 AM8/12/08
to
Hi,
I do not use DataSocket ActiveX VIs. Does anyone seen memory leaks with DataSocket server?
cosmin
I do not use DataSocket ActiveX VIs. Does anyone seen memory leaks with DataSocket server?
cosmin
juliodiaz
Aug 12, 2008, 6:10:06 PM8/12/08
to
Que tal Cosmin,Tuve el mismo problema que tu, usaba LabVIEW DSC 7.0 y migré a LabVIEW DSC 8.6, y como ya han publicado<a href="../view_profile?user.id=95073" class="auth_text" style="font-weight: bold;" target="_blank"></a> Ben y Karunya R, es difícil encontrar la solución a algo si no podemos ver tu problema. Este ejemplo solucionó mi problema, espero solucione el tuyo.Hay algunas cosas que difieren de tu aplicación. Yo estoy usando Win XP SP3. Es recomendable que empieces a considerar cambiar tu sistema operativo a Win XP o Windows Vista, pues Windows 2000 pronto dejará de tener soporte por parte de Microsoft y cada vez será más difícil solucionar tus problemas con este sistema operativo.Saludos, Julio DíazMensaje editado por juliodiaz
DataSocket Memory Leaks.JPG:
http://forums.ni.com/attachments/ni/170/348833/1/DataSocket Memory Leaks.JPG
DataSocket Memory Leaks1.JPG:
http://forums.ni.com/attachments/ni/170/348833/2/DataSocket Memory Leaks1.JPG
jlokanis
Aug 13, 2008, 7:10:07 PM8/13/08
to
Regarding the DS memory leak, would the following VI leak in LV8.5? We call this VI severla times in our code (but not in a loop). Does it matter how many times we call it? Does the leak only happen if we call it several times quickly? Do I need to cache the DS ref so I only call open once? -John
Write Output.vi:
http://forums.ni.com/ni/attachments/ni/170/349169/1/Write Output.vi
Karunya_R
Aug 15, 2008, 5:40:18 PM8/15/08
to
Hi John, I took a look at your VI and it does use DataSocket Active X. An example of a datasocket ActiveX vi is Browse to OPC item.vi in the shipping examples. I tried to run your VI but it looks like you are using an internal IP
address in your VI (which of course I wouldn't have access to). After how long to do you see your memory leak? Have you tried to use the VI profile window to track memory use for your VI. <a href="http://digital.ni.com/public.nsf/allkb/9515BF080191A32086256D670069AB68" target="_blank">This</a> knowledgebase has instructions on it. Thanks,
address in your VI (which of course I wouldn't have access to). After how long to do you see your memory leak? Have you tried to use the VI profile window to track memory use for your VI. <a href="http://digital.ni.com/public.nsf/allkb/9515BF080191A32086256D670069AB68" target="_blank">This</a> knowledgebase has instructions on it. Thanks,
0 new messages