nicost
commented
6 years ago This may be a real memory leak, or it may not be. There are many different types of memory being used by Micro-Manager and not everything gets automatically released all the time. For instance, the JVM manages memory itself, and does not like to give it back to the OS once it has memory allocate.
First. How do you measure memory? You can easily follow memory being used in the JVM itself using ImageJ > Tools > Utilities > Monitor Memory. Clicking the "bar" in the ImageJ windows invokes the JVM garbage collector, always do this a couple of times to force the JVM memory down. However, even when it garbage collects, it does not necessarily release memory back to the OS. So, when you follow memory usage using Windows tools, you may get a false idea that there is a memory leak. On the other hand, images (pixel data) are allocated by Micro-Manager outside of the JVM, and it is potentially possible that these are not garbage collected. That will also show up in the Windows tools. Try running your script multiple times, to see if the application indeed runs out of memory.
Of course, if the memory can not be re-used, then that is a sure sign that something is not right. I would be helped by a fully reproducible test case (using the demo configuration and an acquisition that I can easily reproduce). I ran a test acquisition (using the GUI rather than by script), and saw nothing out of the ordinary (which does not mean nothing as wrong).
nanthony21
I'm Micromanager Gamma using the acquire multiple regions plugin and I notice that the RAM is filling up and causing an error.
The plugin runs the acquisition engine several times. Each time, it recieves the Datastore from the acquisition and then calls freeze() and close().
Datastore store = gui.acquisitions().runAcquisition(currRegion.filename, currRegion.directory); store.freeze(); gui.displays().closeDisplaysFor(store); store.close();
However it doesn't appear that any memory gets freed at
store.close(). Even thought the data store is being saved to disk the data store gets up to around 2GB in the ram. But after the store is closed and thestorevariable is closed this memory sticks around until micromanager is closed.Thanks, Nick