Open Application Reference memory leak

[mattmatt]

I attach a very small vi, that when running in loop, leaks memory.
Is it a bug ?
Salutations
Mattmatt

[chrisger]

hi there

i ran the vi on my system without memory leakage.

Win XPSP2
LV 7.1 PDS

can you try it on another system?

[mattmatt]

It would be difficult to try it on another system.
I will try to find a free computer to make the test.

Some more precisions :
I also have Labview 7.1 PDS (but in french) and Windows XP (Pro) SP2.
The memory leak is quite small (one memory page allocated at about 0.5 or 1 Hz).
The problem is that I use this kind of call in one Labview generated DLL: the program using it has to be stopped each hour to free memory...

Thanks for your test.

Mattmatt

[mattmatt]

I did some more tests, and I have no more idea.

1- On one another computer, with a fresh minimal installation, I do not have the memory leak.

2- I then came back to my computer, uninstalled LabVIEW, erased the National Instruments directory in the Program Files directory, and made a fresh install.
    The memory leak is still there!

Any idea?

Salutations

Matthieu

[chrisger]

hi there

well, try this:

- compare the contents of both LabVIEW.ini files, maybe there's something with the VI- or Web-Server

- clean the registry of the faulty system (e.g. with the demo-version from http://www.tweaknow.com/)

- compare the lists of NI - services and their StartUp-Modes (e.g. Service Locator, License Manager etc.)

- compare the Versions of ALL NI-Software products with MAX -> Software

you said "a fresh minimal installation": what's the difference between the installations on both systems? are there any toolkits or modules like DSC involved?

[mattmatt]

Thanks again for your advices.

>- compare the contents of both LabVIEW.ini files, maybe there's something with the VI- or Web-Server

No effect. A copy of the sane system's labview.ini file does not solve the problem

>- clean the registry of the faulty system (e.g. with the demo-version from http://www.tweaknow.com/)

Work in progress...

>- compare the lists of NI - services and their StartUp-Modes (e.g. Service Locator, License Manager etc.)

I did not find any difference. The only services I identified where :
- NI Service Locator (running on both machines)
- and License Manager (stopped on both machines)

>- compare the Versions of ALL NI-Software products with MAX -> Software

I do not know what MAX is ?

>- you said "a fresh minimal installation": what's the difference between the installations on both systems? are there any toolkits or modules like DSC involved?

- Documentation, Exemples, Proffesionnal tools, Analysis tools, Application Builder, Runtime Navigator Plug-in, LLBs files support
- A new installation with the very same settings on the unsane computer changes nothing regarding the memory leak.

 
Next step : I'm trying to clean the registry of windows...

Best regards

Matt

[chrisger]

hi there

MAX is the "Measurement and Automation Explorer". It's installed at

..\National Instruments\MAX\NiMax.exe

execute it and you'll see an item "Software" in the tree on the left side. mark the entries and get some more information about the NI-Software on your system.

[mattmatt]

Well.

I uninstalled Labview.
Cleaned the registry of windows.
Re-installed Labview.
Same results.

Know, I'm waiting for the new version of Labview (2 days).
And in one month a new computer.
I hope my customer will wait: the tricky part is that the DLL generated shows the same behaviour.

I also have to try to generate it on another computer to see if this is still the case...

The usual way to solve the bugs I discovered in Labview since I began to use it in 1992...
Just pay, and have a new version installed.

Thanks again

Matt

[chrisger]

well,

is it possible to post some (condensed) code? does the dll show the memory leak even when its compiled on a system where your little test-vi shows no leakage?

[Ben]

This is not a bug.

Every time you ask LV to get a reference to something, it will allocated memory to manage that resource. The memory allocated is not released until after you exit LV.

The proper way to do something like this is to open the reference once, re-use the same reference reapeatedly (in a while loop) and then close it ater everything is done.

So,

Not a bug.

Ben