HelloI've been programming a GUI for a project. The basics of the program is a sample routine that updates a array once a second. Once the array is updated I use a event handler to plot the new array in a graph. When I wrote this gui I think I've stumbled upon a bug in Labviews memory allocation.If you have two loops. One that builds a array and then signals a loop with a eventhandler that reads the array and the event handler is stoped for a few seconds (by opening a sub vi or something inside the event handler), the memory goes berserk. When the event handler is free after the stop the memory is still allocated and does not return.I could not find any information on this problem in the forum so I thought I would share this information with everyone. I managed to reproduce this phenomena in a small example (attached), if anyone is interested in it. The problem is simple to fix once you recognize the problem. However it was not the simplest problem to find (imho that is ;)).RegardsAndreas Beckman

LabVIEW

Event handler eats up memory. Bad programing and/or bug.

Hello!

I ran your example on a Redhat Linux 8 machine and then on my Windows XP SP2 machine and the amount of memory reported by File>VI Properties>Memory Usage or alternatively Tools>Advanced>Profile VIs with 'Memory Usage' + 'Profile Memory Usage' enabled shows the similar memory usage on both systems when running the example for approximately the same amount of time and opening the subVI the same number of times. So I cannot see any indication of a memory leakage in LabVIEW.

Regards,
Jimmie A.
Applications Engineer, National Instruments

Regards,
Jimmie Adolph
Systems Engineering Manager, National Instruments Northern European Region

Message 11 of 11

(296 Views)

LabVIEW

Event handler eats up memory. Bad programing and/or bug.

Re: Event handler eats up memory. Bad programing and/or bug.