memory problem

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

memory problem

Michael Cammer
We've installed ImageJ 1.38t with Java 1.5 on a dual processor
Windows XP machine and are having the following memory problem.

We're opening 3 8bit files of 88 MB each.

Before opening them, the ImageJ memory monitor says 1.24 MB is being used.
After opening them, it says 525 MB is being used.

Before opening them, the Windows memory monitor says approx 214 MB of
memoy is being used.
After opening them, it says 1 GB of memory is being used.

We try to color merge the three images and ImageJ returns an error
message and closes the three windows.

Now ImageJ claims that 349 MB is being used and Windows has increased
committed memory to 1.21 GB.

This is only one example of memory problems we're having.

Any suggestions?

Thanks!
____________________________________________________________________________
Michael Cammer   Analytical Imaging Facility   Albert Einstein Coll. of Med.
URL:  http://www.aecom.yu.edu/aif/ 
Reply | Threaded
Open this post in threaded view
|

Re: memory problem

Michael Cammer
Also, the Garbage Collect macro posted here on 2 June 2005 only works
sometimes to free up memory.

Other times multiple calls don't help.

For instance, memory gets tied up to 1.24 GB but the only image open
is 113 MB 8bit grayscale.  Calling GarbageCollect_.class multiple
times only reduces committed memory to 1.08 GB.

-Michael


At 09:05 AM 06/11/07, you wrote:

>We've installed ImageJ 1.38t with Java 1.5 on a dual processor
>Windows XP machine and are having the following memory problem.
>
>We're opening 3 8bit files of 88 MB each.
>
>Before opening them, the ImageJ memory monitor says 1.24 MB is being used.
>After opening them, it says 525 MB is being used.
>
>Before opening them, the Windows memory monitor says approx 214 MB
>of memoy is being used.
>After opening them, it says 1 GB of memory is being used.
>
>We try to color merge the three images and ImageJ returns an error
>message and closes the three windows.
>
>Now ImageJ claims that 349 MB is being used and Windows has
>increased committed memory to 1.21 GB.
>
>This is only one example of memory problems we're having.
>
>Any suggestions?
>
>Thanks!
>____________________________________________________________________________
>Michael Cammer   Analytical Imaging Facility   Albert Einstein Coll. of Med.
>URL:  http://www.aecom.yu.edu/aif/

____________________________________________________________________________
Michael Cammer   Analytical Imaging Facility   Albert Einstein Coll. of Med.
URL:  http://www.aecom.yu.edu/aif/ 
Reply | Threaded
Open this post in threaded view
|

Re: memory problem

dscho
Hi,

On Mon, 11 Jun 2007, Michael Cammer wrote:

> Also, the Garbage Collect macro posted here on 2 June 2005 only works
> sometimes to free up memory.
>
> Other times multiple calls don't help.
>
> For instance, memory gets tied up to 1.24 GB but the only image open is
> 113 MB 8bit grayscale.  Calling GarbageCollect_.class multiple times
> only reduces committed memory to 1.08 GB.

Some operations actually store more than meets the eye. For example, if
you run Fourier transform, there are quite a few arrays which take
_multiple_ times the original images' size, but which are needed for the
inverse transform, AFAICT.

Ciao,
Dscho