NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: java.lang.OutofMemoryError



Thanks Bill. I had another question regarding openmap. Has anyone
used openmap with visad. Or if VisAD can read a map database such 
as DCW and display it.


Thanks,

Nash'at


On Wed, 8 Nov 2000, Bill Hibbard wrote:

> Hi Nash'at,
> 
> > I ran it using java -mx256m and I was able to do a lot of re-displays
> > before I got that error again. I have a question though- I thought that
> > Java does automatic memory management. Once I clear the display, it should
> > release all the memory, but it seems that somethings are kept causing
> > the application to crash at a later time. Can you give some insight
> > on this?
> 
> I just took a quick look at your code.  I think the problem
> may be that you always construct a 'new TerrainView()' in
> the actionPerformed() method of OmegaWindowManager.  The
> new TerrainView() constructs all sorts of objects with Threads
> and connections to AWT and Java3D that do not go away just
> because you replace your own reference 'terrView' in the
> next call to actionPerformed().  I suggest creating some
> methods for TerrainView so that you can re-use it for new
> data, and only construct 'new TerrainView()' once.
> 
> Good luck,
> Bill
> ----------------------------------------------------------
> Bill Hibbard, SSEC, 1225 W. Dayton St., Madison, WI  53706
> hibbard@xxxxxxxxxxxxxxxxx  608-263-4427  fax: 608-263-6738
> http://www.ssec.wisc.edu/~billh/vis.html
> 



  • 2000 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the visad archives: