-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TrackMate does not free up RAM when closing. #185
Comments
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/trackmate-does-not-free-up-ram-when-closing/54922/4 |
@tinevez I'm curious to know how you deal with this. Visualvm + eclipse MAT? |
I am actually using the YourKit Java profiler, making a RAM snapshot. |
Hum I am afraid I am failing big time on this one. |
@tinevez Just a guess: is it possible that some I pushed a branch Do you have any frames that you allow the user to toggle visibility by closing them temporarily? Like, they can press the X, but then another button elsewhere can show the frame again? If so, we'd need to do something more clever to dispose such frames at the proper time later. |
If I track a 250MB image (one coming from the ISBI SPT challenge, VIRUS snr 7 density high) I see it at the end of the tracking. I document here quickly the RAM usage followed with the Monitor Memory tool (it is not relevant to check RAM usage from the Windows tool).
Every value I report are the one reported by the tool after garbage collection.
I used the devel version of TrackMate for the test.
Opening Fiji
43 MB
Opening the Image
295 MB
Launching TrackMate
480 MB
In the config panel of the LoG detector, after preview
310 MB (sigh)
If I close TrackMate UI and the image now, the RAM usage goes down to 58 MB, which is what we expect.
After full detection (diameter 5, threshold 50, no initial thresholding, I got about 100k spots), in the spot filter panel
530 MB
If I close TrackMate now, it does NOT give back the RAM. I still use 530 MB
So here is my memory leak.
The text was updated successfully, but these errors were encountered: