To share some insight on how I handled and localized the issue, this post summarizes some basics to discover possible memory leaks using Eclipse Memory Analyzer.Īfter a quick search of our recent major commits, I couldn’t find any change that would cause a heap problem. Of course, this is one of the most shocking log entries for any developer. Analyzing large Java heap dumps when Eclipse Memor.Recently I was informed about some : Java heap space issue found in one of our application logs.The tool seems to be closed source and is very sensitive to heap dump corruptions.Īs an aside, here's something that might be useful for the initial heap dump quickly. Being a sampling reader, the output is also a little imprecise but helps a great deal when you have nothing else. It is a sampling heap dump reader and so it works for very large heap dumps where MAT sometimes fails. Has HTML files just like the MAT Eclipse UI. Output is a small and easy to download jvm_Leak_Suspects.zip. Step and run a "Leak suspects" report on the heap dump. Then use the indices created in the previous Takes a while to execute and generates indices and other files to make Fortunately, there is a script that comes with MAT to parse the the heap dump and generate HTML reports without ever having to launch Eclipse! It's just that the command line option is not well advertised.Ĭommand line heap analysis using Eclipse MAT:Įclipse MAT is installed and we are inside the mat/ directory, modify MemoryAnalyzer.ini heap settings to use a large heap to handle large Launching Eclipse and updating the UI is an extra load on the JVM that is already busy analyzing a 30G heap dump. However, trying to get the UI to run remotely is very painful. only to find out that X-over-SSH is too slow then this article is for you.Īs of Nov 2013, we have 2 options - Eclipse MAT and a hidden gem called Bheapsampler.Įclipse Memory Analyzer is obviously the best tool for this job. If you find yourself trying to analyze a big heap dump (20-30GB) downloaded from your production server to your staging/test machines.
0 kommentar(er)
