[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

--- Comment #2 from Curtis Rueden <ctrueden at wisc.edu> ---
Note that while it is expected to see an ever-increasing RAM usage in Task
Manager, what is _not_ expected is to receive OutOfMemoryError in ImageJ while
working with a single image at a time. Java should be reusing memory
internally. So if you indeed _need_ to restart ImageJ every 3 images as you say
due to OutOfMemoryError, that would constitute a real memory leak. And as Jan
suggests: instructions to reproduce would be very helpful.

-- 
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/a19f8209/attachment.html>