Ricardo,
Have you tried increasing the JVM's maximum heap size?
The command is:
java -mx128m JavaApp
where "JavaApp" is your application, and "128" is the number
of megabytes maximum memory you wish to grant the JVM.
If you still receive OutOfMemoryErrors, then Jim's analysis
is probably accurate in that you simply do not have enough
memory to deal with a dataset of that size.
Curtis
At 15:05 5/31/00, Jim Edwards wrote:
>You are asking for 96+MB (assuming 4 bytes per element) of memory to store
>one array!
>Double that if one of your calls required a copy.
>
> I assume you are running unix?
>
>First make sure you have that much memory available on your system, run:
>$ ulimit -a
>
>that should tell you how much memory you have available and how much of
>that can be used for data.
>Note that lots of things other than your program need to reside in memory
>so you can't use it all.
>If these numbers do not correspond to the amount of memory you think you
>have:
>1. Make sure you really have as much as you think you have.
>2. Find out (probably from your sys-ad) how to get access to more of it.
>It may be possible to
> increase your memory alotment as user but most systems require root
>access to do so. (try $ man ulimit)
>
>
>If you're lucky that's your only problem, but I suspect there may also be
>java related issues.
>Good Luck.
>
>Jim
>
>
>Ricardo Ivan Mantilla G wrote:
>
> > Hello visad Users:
> >
> > Somebody knows how can i solve this error?
> >
> > java.lang.OutOfMemoryError:
> > at visad.FlatField.unpackValues(FlatField.java:882)
> > at visad.FlatField.unpackValues(FlatField.java:846)
> > at visad.FlatField.computeRanges(FlatField.java:3457)
> > at visad.DataImpl.computeRanges(DataImpl.java:556)
> > at visad.DataRenderer.prepareAction(DataRenderer.java:200)
> > at visad.DisplayImpl.doAction(DisplayImpl.java:879)
> > at visad.java2d.DisplayImplJ2D.doAction(DisplayImplJ2D.java:308)
> >
> > at visad.ActionImpl.run(ActionImpl.java:193)
> > at visad.util.ThreadPool$ThreadMinnow.run(ThreadPool.java:86)
> >
> > It occurs when I load data of a 2000 x 2000 x 6 image into a dysplay
> >
> > thanks
> > Ricardo
