User:Steven J. Koch/Notebook/Kochlab/2009/07/09/Feedback 96, Memory Leak
Steve Koch 22:12, 9 July 2009 (EDT): There is some kind of memory leak...in "non-acquisition mode" (before pushing "set"), the amount of memory steadily increases at about 2 MB per second it seems. It will keep going until LV eats up all of the 2 GB or whatever of RAM and then crashes. It does not do this in "acquisition" mode. But you don't recover the memory until you stop running the program.
- Steve Koch 22:27, 9 July 2009 (EDT): Found it! It was in the VI that discovers the bit resolution. I was trying to release the resources (I copied the method from the express VI or at least I think I did), but not succeeding. I added the "clear task" as well, and it now seems to work. I should add this in the other places I do this as well.
cool--I've now checked various scenarios in feedback96, and I don't see any huge memory leaks. I added in all those clear tasks first. Memory usage is about 77 MB which seems OK.