my out of mem error is/was due to the failure of GZIPOutputStream to release its memory fetched outside of GC. I used "top" to display the amount of mem used by the active process. If that grows larger as your GC stays the same, then u have a mem leak outside of GC. I then looked at the contents of /proc/PID/maps . These are memory mappings for large chunks of main memory. If u have a lot of them with no ownership ( ie to a library ) then u are losing it that way. But now u have a way to localize when MORE chuncks are allocatoed but not released. Sometimes I get an outta memory message because the Awt/graphics eats up too much memory. remember that some objects do not release their resources even if the object is completely destroyed! ( this is sometimes the fault of the JVM in its inability to process finalize properly - if at all )
/gat kulkarni sourabh wrote: > > Hi Alexander, > I have traced through my code thoroughly and there > is no memory leak. I > have also printed the Garbage Collector's output. The > hil to > > [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] > > > > __________________________________________________ > Do You Yahoo!? > Find the one for you at Yahoo! Personals > http://personals.yahoo.com > > ---------------------------------------------------------------------- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
