Comments on: How to Fix Memory Leaks in Java

By: Phung Nam

Phung Nam — Mon, 08 Mar 2010 04:52:02 +0000

Thanks you for great article !

By: sudha

sudha — Tue, 16 Feb 2010 04:14:33 +0000

Very well written article. Thanks for sharing the knowledge.

By: Santosh

Santosh — Thu, 05 Nov 2009 12:42:26 +0000

Its a sound, Understandable and detail explanation about memory leakage. Thank you very much.

By: Michael Brown

Michael Brown — Wed, 21 Oct 2009 21:33:57 +0000

Excellent article!! Well done with the right perspective and detail to allow for real life application. I will be referring to this article for others and keeping it bookmarked myself.

By: Wazi » Features Tutorials » Checking Basic Life Signs of Applications Running In JBoss

Tue, 15 Sep 2009 19:12:36 +0000

[...] Memory leaks are slightly more complex. For additional details on fixing memory leaks please see the tutorial, How to Fix Memory Leaks in Java. [...]

By: Harshit

Harshit — Wed, 01 Jul 2009 06:09:10 +0000

Very well explained . Nice comprehensive article. Feels like reading a nice fairy tale . Will put this link in my post.

By: Ashok

Ashok — Sat, 23 May 2009 18:18:37 +0000

Very good article … Thumbs up for this one …

By: Renan Huanca

Renan Huanca — Thu, 19 Mar 2009 15:33:57 +0000

Hi, can i translate it to spanish an put it to my blog?. of course I will name the source
The article is very good.

By: Esteban

Esteban — Wed, 18 Mar 2009 14:02:04 +0000

Great Article. Thanks. If you’re working with JDK 1.4, from 1.4.2_12 you can use -XX:+HeapDumpOnOutOfMemoryError or -XX:+HeapDumpOnCtrlBreak. -XX:-HeapDumpOnOutOfMemoryError also works in 5.0 update 7 (http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp). I have also used the IBM HeapAnalyzer (http://www.alphaworks.ibm.com/tech/heapanalyzer) to analize the heap dumps (but itself can throw OutOfMemoryError if you don’t have lots of ram analizing a big dump). Sun’s VisualVM is great.

By: Un buen articulo sobre como resolver Memory Leaks en Java « Myndbackup

Un buen articulo sobre como resolver Memory Leaks en Java « Myndbackup — Thu, 12 Mar 2009 20:33:07 +0000

[...] http://olex.openlogic.com/wazi/2009/how-to-fix-memory-leaks-in-java Possibly related posts: (automatically generated)Refactor your Java Code-06 (using WeakHashMap)Performance improvement on memory leakFree Java Profiling Tools [...]

By: Tom Chikoore

Tom Chikoore — Thu, 12 Mar 2009 18:56:28 +0000

Great post. Well researched and well written. I will definitely add this to my list of great cookbooks.

By: links for 2009-03-12 « Brent Sordyl’s Blog

links for 2009-03-12 « Brent Sordyl’s Blog — Thu, 12 Mar 2009 14:03:53 +0000

[...] How to Fix Memory Leaks in Java In addition, keep in mind that Java GC is not a constant process—it runs in intervals. The memory usage that you see in the JVM is usually higher then what your program needs at the moment, as GC hasn’t yet run. Remember, lazy bachelors usually have some trash in their apartments waiting to be taken out. (tags: java debugging howto memory) [...]

By: Markus Kohler

Markus Kohler — Thu, 12 Mar 2009 09:49:51 +0000

Posted your article to http://www.dzone.com/links/index.html and it’s NR 5 currently
BTW Netbeans has a very nice profiling feature that shows you Garbage Collector generations.
It’s very helpful for finding leaks.

By: Puneet Lamba

Puneet Lamba — Wed, 11 Mar 2009 23:59:46 +0000

This is a very crisp and comprehensive explanation of how to manage memory leaks. Thank you.

By: stanasic

stanasic — Wed, 11 Mar 2009 21:36:07 +0000

Great article, covered all the bases pretty well. Kudos for all the hard work that went into this one.

By: Cédrik

Cédrik — Wed, 11 Mar 2009 18:18:52 +0000

Excellent article, very clear and well written!

I’ve had a good experience with YourKit while tracking a nasty memory leak, as described at http://www.jroller.com/javabean/entry/solving_an_outofmemoryerror_java_6
If you are ever using File.deleteOnExit() or a JDBC driver, go have a look at said article for a solution.

By: Chuck Simpson

Chuck Simpson — Wed, 11 Mar 2009 16:49:13 +0000

Nice article! You covered heap-based leaks very well.

Don’t forget that leaks can occur due to other causes as well. Native libraries can leak and tuning problems can masquerade as a leak. One of the more difficult leaks I had to find was caused by fragmentation of the swap area due to a high thread count and the default native stack size. Decreasing the stack size plugged the leak.

By: Alain G

Alain G — Wed, 11 Mar 2009 16:14:08 +0000

Great post!

On occasion i’ve also used AspecJ to monitor the add and get methods of collections (outing the size helps) and maps since most errors occurred there. I’ve seen people overriding the Hash method with System.currentTime and also messing up the Equals contract

By: Markus Kohler

Markus Kohler — Wed, 11 Mar 2009 08:39:51 +0000

Excelllent post!
This is almost exactly the way I attack memory leak problems.
You mention the Eclipse Memory Analyzer you might be interested in my post here http://kohlerm.blogspot.com/2009/02/memory-leaks-are-easy-to-find.html