>On Tuesday 30 January 2007 21:37:47 Gib Bogle wrote:
>
>
>>Albert, the behaviour I'm seeing is creating much more lost memory than
>>this. The amount of memory lost is about twice the size of the tif
>>file. I should emphasize that this occurs when doing nothing else other
>>than File>Open and Image>Color>RGB Split. That is, immediately after
>>starting ImageJ:
>>
>>Plugins>Utilities>Monitor Memory
>>File>Open test.tif
>>Image>Color>RGB Split
>>close 3 image windows
>>
>>Memory usage is now about 10 MB. Repeat the above steps and 10 MB is
>>added to the memory usage each time (when test.tif is 4.7 MB).
>>
>>
>
>I am testing this in linux with java 1.6
>
>for(i=0;i<100;i++){
> open("/home/gabriel/ImageJ/f00.tif");
> run("RGB Split");
> close();
> close();
> close();
>}
>
>The file is a 9MB rgb. One run of the macro (100 times open split and close)
>does not increase the memory use as reported by the memory monitor.
>
>
>Gib, although you said in a message that you installed the latest version of
>IJ, then you said :
>
>
>
>>I have ImageJ version 1.37v, Java version 1.5.0_11, Windows
>>
>>
>
>Note that 1.37 is not the latest but 1.38h is.
>
>Check:
>
>
http://rsbweb.nih.gov/ij/notes.html>
>Not sure if this applies to the behaviour you found but lots of people report
>bugs on old versions. It is more useful -if one finds some strange behaviour-
>to upgrade first to the ij.jar file using the link above and see if the
>problem persists.
>
>Cheers,
>
>Gabriel
>
>
be the latest version. I have now done as you suggest (thanks) and
installed 1.38h. The problem persists. BTW, for this testing I'm doing
the file open and RGB split manually, not using a macro as you are.