Re: Tracking down unwanted object retentions that are eating memory

    Hi James,

    Yours is such a wide open question that I think about all you're going
to get for responses is "use a profiler/optimizer", as you've already seen.
Without reviewing the code, the only things that come to mind are:

    If you have *lots* of threads, there used to be ( and maybe still is ) a
bug in ThreadGroup ( I think ) that never released a reference to a thread.

    If you use substrings, for performance, they reference the original
String.  While I think there was some work done on it, it can mean that
Strings you think are available for gc really aren't.

    HTH, but I learned a long time ago that I'm not psychic.


                                                         Joe Sam

Joe Sam Shirah -        http://www.conceptgo.com
conceptGO       -        Consulting/Development/Outsourcing
Java Filter Forum:       http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International?    http://www.jguru.com/faq/I18N
Que Java400?            http://www.jguru.com/faq/Java400


----- Original Message ----- 
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
To: <java400-l@xxxxxxxxxxxx>
Sent: Wednesday, May 17, 2006 6:04 PM
Subject: Tracking down unwanted object retentions that are eating memory


> We have a situation in which the latest experimental
> version of one of our Java client programs is devouring
> memory like cuckoo, apparently from something retaining
> references to obsolete objects.
>
> Nobody here can see what could be causing it.
>
> Does anybody here have any suggestions on how to track
> down unwanted object retentions?
>
> The client in question works either as an application, or
> an applet, or as a webstart.
>
> --
> JHHL
> --