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: Image capture -- renegade threads

> You might try running under jdb, then after the destroy()
> use the 'suspend all' command followed by 'where all',
> which should list all the Threads. If you do this, please
> send us the output of 'where all'.

I'll give this a try.


> Another thought: if you want to capture a series of
> iamges, can you call DisplsayImpl.removeAllReferences()
> and/or DisplayImpl.clearMaps() between images, then re-use
> the DisplayImpl?

Yeah.  That would probably be the better way to go.  But, I
seem to have memory problems after awhile and I'm wondering
if the memory issues are related to the thread issues.

Leah


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