Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.

Re: Memory problems with VisAD (Oops)

I had the same problem and Bill Hibbard gave me this solution which worked
for me.  He said:

>
> I am not sure where the memory leak is. However, it should not
> be necessary to completely destroy your DisplayImpl in order to
> change its properties. The following two calls should do it:
>
>   display.removeAllReferences();
>   display.clearMaps();
>
> Please let us know if these don't solve your problem.

Luke

----- Original Message -----
From: "Mathias Stümpert" <atzes@xxxxxx>
To: "VisAD List" <visad-list@xxxxxxxxxxxxx>
Sent: Monday, December 17, 2001 2:35 AM
Subject: Memory problems with VisAD (Oops)


>
> Forgot the example program, sorry.
>



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