Posted by
Joachim Wesner on
URL: http://imagej.273.s1.nabble.com/Remove-slices-from-a-virtual-stack-tp3690894p3690897.html
Hi Eddie,
This is probably no problem at all!
It is a common misconception that "free memory" is "good memory", maybe
even dating back to the time of the old Commodore C64. Newer operating and
runtime system will keep their
old memory as long as possible and/or use it as a quick memory backup
storage for files. In this way, "free memory" is "bad memory", because it
is unused/idle memory!
This may be very dramatic for example under Linux, where people often ask,
"I now have x GB of memory in my system, but after working for a long time,
it´s almost all gone, what is going wrong?"
Nevertheless, a working OS/VM should trigger a garbage collection, if
another tasks really request his own memory and finally release enough
ememory for the request,
This might cause a slight delay compared to the case that memory was
already "free" before the 2nd task was started, but the overall benefit of
trying to almost always benefit from ALL available memory in some way, is
generally considered larger!
You can however limit the maximum memory ImageJ will ever use in it´s
config file!
See also:
http://imagejdocu.tudor.lu/doku.php?id=howto:general:imagej_performance_tuninghttp://imagejdocu.tudor.lu/doku.php?id=faq:technical:how_do_i_increase_the_memory_in_imagejMit freundlichen Grüßen / Best regards
Joachim
____________________________________________
Leica Microsystems CMS GmbH | GmbH mit Sitz in Wetzlar | Amtsgericht
Wetzlar HRB 2432
Geschäftsführer: Dr. Stefan Traeger | Dr. Wolf-Otto Reuter | Dr. David Roy
Martyr | Colin Davis
www.leica-microsystems.com
Eddie Iannuccelli
<eddie.iannuccell
[hidden email] An
R>
[hidden email]
Gesendet von: Kopie
ImageJ Interest
Group Thema
<
[hidden email]. How to release memory
GOV>
23.09.2009 15:01
Bitte antworten
an
eddie.iannuccelli
@toulouse.inra.fr
Hello,
my java application use ImageJ (1.41) as a library, I noticed that
memory always grows but never decreases so I made a test directly on
ImageJ. When starting ImageJ, the MS Windows task manager show a memory
occupation of 21 MB, after opening a stack the memory occupation is
about 76 MB, after the stack is closed, the memory never decreases. The
ImageJ internal memory manager show the same memory retention, the same
issue occurs under Linux.
How can I fix this problem, is it an ImageJ problem or a java memory
management problem ?
Regards
--
******************************************
Eddie Iannuccelli
Laboratoire de génétique cellulaire
INRA - Castanet Tolosan
Tel: 05 61 28 54 44 / Fax: 05 61 28 53 08
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit
http://www.messagelabs.com/email
______________________________________________________________________