From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
07-12-2005 02:37 AM
07-12-2005 05:05 PM
07-12-2005 09:23 PM
The quickest way of identifying this problem is if you could post the VI that you are working on.
Mike...
07-13-2005 01:35 AM
Hi, thanks about your post.
About your question how i know that there is memory leaking problem - i look in Task Manager and see that excel running after closing it.
"Case" - i mean LabVIEW switch structure that include number of cases. I have 2 "cases", each of them include creating Excel object "Sheet", but really only 1 of them created.
Please look attached llb. This is NI Excel example, but have 1 changing: in VI that open new sheet i added case that include 2 identical cases, just for understanding where is a problem.
07-13-2005 07:03 AM
Ok, the code is doing exactly what it's supposed to be doing (almost--there is still a real memory leak issue, but we'll get to that in a moment). There is a font panel control called Completion Task that has the default value "Leave Excel Open" so you it leaves Excel running--you're telling it to.
Now having said that, there is still a problem. The only time that LV's Application and WorkBook RefNums are closed is when you close the application. The two close nodes need to be outside the final case structure so the references get closed regardless of whether the program is left running.
Mike...