[ImageJ-bugs] [Bug 1163] ImageJ doesn't release memory after closing an image

[bugzilla at fiji.sc]

http://fiji.sc/bugzilla/show_bug.cgi?id=1163

Jan Eglinger <jan.eglinger at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |jan.eglinger at gmail.com
         Resolution|---                         |INVALID

--- Comment #1 from Jan Eglinger <jan.eglinger at gmail.com> ---
(In reply to Fred from comment #0)
> Created attachment 261 [details]
> Taskmanager showing accumulating memory usage
> 
> When I analyse large images (1GB per image), then the memory is not released
> when I close the image and open a second. Only when closing the ImageJ
> application, the memory is released. Very annoying when analysing such
> images and have to restart Image J after each three images.
> 
> Regards, Fred Mellink

Please have a look at the explanatory box here:
http://wiki.imagej.net/Troubleshooting#Common_error_messages

"This is a characteristic of the Java runtime. In many cases, Java never
releases memory back to the system, so memory monitors such as Windows Task
Manager will always report an ever-growing amount of RAM used by the Java
process, until the JVM shuts down."

If you see accumulation of memory even within ImageJ using 'Plugins > Utilities
> Monitor Memory...', please reopen this issue with more information how to
reproduce.

Jan

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-bugs/attachments/20150924/97c69886/attachment.html>