Re: Memory leak in Radar App

• To: dmurray@xxxxxxxxxxxxxxxx
• Subject: Re: Memory leak in Radar App
• From: "Tom Whittaker" <tomw@xxxxxxxxxxxxx>
• Date: Tue, 21 Feb 2006 09:11:06 -0600

Hi Don...

Tom Rink and I were just talking -- we think this issue (hidden
window) has come up before. Maybe you could run this with -verbose:gc
and see if the G.C. is running when the window is hidden...or not...?

tom

On 2/20/06, Don Murray <dmurray@xxxxxxxxxxxxxxxx> wrote:
> I have an update on this issue:
>
> Don Murray wrote:
>
> > - when I run this using copy=false, my max heap
> > gets up to 89 mb and then stays there.   I added
> > in our ucar.unidata.util.MemoryMonitor widget to
> > keep track of the memory usage and commented
> > out it's call to run garbage collection so that
> > wouldn't affect the results.
>
> When I wrote this original message, I was not seeing
> the memory spikes that James sees.  My memory usage
> would level off at 89 mb. However, if I
> minimize the display window or have the window hidden
> by the readout window, the memory spikes up quickly.
>
> I'm not sure what to make of this.  I suspect that
> Jame's variations in how many iterations it takes
> to run out of memory depends on how long
> the canvas is hidden during the tests. ;-)
>
> Don
> *************************************************************
> Don Murray                               UCAR Unidata Program
> dmurray@xxxxxxxxxxxxxxxx                        P.O. Box 3000
> (303) 497-8628                              Boulder, CO 80307
> http://www.unidata.ucar.edu/staff/donm
>          "Time makes everyone interesting, even YOU!"
> *************************************************************
>
>
>


--
Tom Whittaker
University of Wisconsin-Madison
SSEC/CIMSS
1225 W. Dayton Street
Madison, WI  53706  USA
ph: 608-262-2759

• References:
  • Memory leak in Radar App
    • From: James Kelly
  • Re: Memory leak in Radar App
    • From: Don Murray
  • Re: Memory leak in Radar App
    • From: Don Murray