Memory leak in DIADEM 8.1

[matadler]

Hello,

I'm using DIADEM 8.1.1292 on a 3GHz WinXP ProSP2-PC with
2Gytes of RAM.
I'm doing some extensive data manipulation with DIADEM-VBScript and discovered (?) a memory leak which seriously disturbs my work:

After finishing the script DIADEM doesn't free the used memory (RAM). I checked this behaviour using XP task manager. After starting DIADEM, it uses about 300MBytes . During my Script the memory consumption goes up to over 1Gbyte. After successfully finishing my script DIADEM doesn't free the Windows memory. Next time I run my script DIADEM stops with an error at about 1,5Gbyte memory consumption.
If I restart DIADEM everything works fine until the memory is full again.

Any hints? How can I tell DIAdem to free the memory?

Than
ks in advance
Mathias

[Brad_Turpin]

Hi mstadler,

My guess is that if you are talking about the DIAdem thread using over a Gigabyte of memory, your VBScript must be creating new DATA channels. If that's the case, then let me ask: when you re-run your VBScript, does it first delete the new channels it created the first time? Would you be willing to send over the VBScript you are running for us to take a look at it? You may well have discovered a memory leak, but based on your description my suspicion is that we can avoid this behavior by changing the details of the VBScript and perhaps other memory management properties. Does your VBScript load data from a file? Could it perhaps register that data instead (File>>Register file...)? Your operating system will only give DIAdem (or any other W
indows application) up to but not exceeding 2 GBytes of virtual memory. DIAdem has the ability to manage its own virtual memory far in excess of this limit, but in DIAdem 8.1 this still has to be manually preconfigured. In DIAdem 9.1 the DIAdem-managed virtually memory automatically kicks in when needed and configures itself.

Please send over your VBScript if that's feasible,
Brad Turpin
DIAdem Product Support Engineer
National Instruments