Analyze Java memory leak problem with Eclipse Memory Analyzer
2009-11-24 07:00
465 查看
Well the Eclipse Memory Analyzer is really a cool tool. Actually it’s just a plug-in for Eclipse. It is designed to analyze the Java dump file and it tries to automatically generate the report of the dump file and it can even detect the possible issues that occurs in the dump. Amazing.
Most of the belowing checking points are just summarized from these two links, thanks for their guide.
http://www.blogjava.net/justinchen/archive/2009/02/22/256113.html
http://blog.csdn.net/moneyice/archive/2008/07/12/2644503.aspx
So firstly we need to get some Jave Heap Dump and then open it with Memory analyzer.
- Check the overview chart and if u’r lucky enough the most critical memory-consuming part can be easily checked out in this step.
- Check the thread list, and find the top ones, use ‘List Objects’->'with incoming refrence’ to find the class’s caller.
- Exclude the weak calls by ‘Path to GC roots’ –> 'exclude weak/soft references’ and get the parts left.
- Track it back and find the root cause in the source code.
But remember the most important thing, don’t forget to bring your source code. Without the source code, any imagination by the class name is just a guess.
Most of the belowing checking points are just summarized from these two links, thanks for their guide.
http://www.blogjava.net/justinchen/archive/2009/02/22/256113.html
http://blog.csdn.net/moneyice/archive/2008/07/12/2644503.aspx
So firstly we need to get some Jave Heap Dump and then open it with Memory analyzer.
- Check the overview chart and if u’r lucky enough the most critical memory-consuming part can be easily checked out in this step.
- Check the thread list, and find the top ones, use ‘List Objects’->'with incoming refrence’ to find the class’s caller.
- Exclude the weak calls by ‘Path to GC roots’ –> 'exclude weak/soft references’ and get the parts left.
- Track it back and find the root cause in the source code.
But remember the most important thing, don’t forget to bring your source code. Without the source code, any imagination by the class name is just a guess.
相关文章推荐
- Analyze Java memory leak problem with Eclipse Memory Analyzer
- How to use Eclipse Memory Analyzer to analyze JVM Memeory Issue
- Eclipse Memory Analyzer(Java内存泄漏分析工具)
- eclipse:Exception in thread "http-bio-8080-exec-11" java.lang.OutOfMemoryError: PermGen space
- Java memory profiling with jmap and jhat
- OOM与Eclipse Memory Analyzer
- 在eclipse中的tomcat中出现报错 Java.lang.OutOfMemoryError: PermGen space
- 解决Eclipse和MyEclipsejava.lang.OutOfMemoryError Java heap space的错误
- 性能分析工具之-- Eclipse Memory Analyzer tool(MAT)(三)
- eclipse内存溢出报错:java.lang.OutOfMemoryError:Java heap space
- Eclipse--java.lang.OutOfMemoryError: PermGen spac
- Handling Java Memory Leak
- eclipse内存溢出报错:java.lang.OutOfMemoryError:Java heap space.
- 解决eclipse maven install 造成JVM 内存溢出(java.lang.OutOfMemoryError: Java heap space)
- Eclipse+Maven+Jetty 环境下java.lang.OutOfMemoryError: PermGen space及其解决方法
- Eclipse : Class file name must end with .class exception in Java Search
- Eclipse中java.lang.OutOfMemoryError: Java heap space 的问题解决方法
- eclipse java.lang.OutOfMemoryError: Java heap space
- eclipse启动tomcat中出现java.lang.OutOfMemoryError: PermGen space 解决办法
- Eclipse – java.lang.OutOfMemoryError: Java heap space解决方案