Get Object Memory Leak

[EthanHenry]

Thank you for your input!  I understand that it doesn't seem like it grows much, and I do have to admit that it looks unlikely from here, but I am using Simulated hardware, not the hardware itself.  One person, who ran the program for a long time, reported that it caused some funky stuff to happen to their computer, eventually crashing it.  Retrieving their Windows logs, it shows that windows detected a resource exhaustion point, and reported that the EXE was using around 1000 MB of memory (1027473408 bytes to be exact).  It then reported that an svchost.exe had an overrun of it's stack-based buffer, which I am assuming led to all the funky stuff that happened afterwards.  I guess since I can't emulate it on my computer maybe the problem is in the hardware drivers?  I guess that progress in it's own way.  I'll keep looking, but I appreciate any more advice anyone has.  Thanks!

[rolfk · Accepted solution]

svchost.exe is definitely NOT directly related to LabVIEW. That's a Microsoft helper program used to run certain services. As such your guess that it has probably more to do with the hardware drivers for the hardware in question has a very high probability to be true. And 1GB of memory allocations after a long time of running for an application that starts up with a 900MB memory footprint is anything but alarming to me. If it was LabVIEW 32-bit and you were close or beyond the 2GB mark, then I would start to wonder a little more. But 1GB of memory consumption with the memory consumption graph as you have shown, means to me one thing and one thing only: Keep looking elsewhere, you have not found the problem yet!

Even the chance that it was a random Windows hiccup caused by some magic cosmic ray hitting the wrong transistor at the wrong moment has a higher probability here.