Analyze Java memory leak problem with Eclipse Memory Analyzer

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.

posted @   Raymond Zhang  阅读(611)  评论(0编辑  收藏  举报
编辑推荐:
· ASP.NET Core 模型验证消息的本地化新姿势
· 对象命名为何需要避免'-er'和'-or'后缀
· SQL Server如何跟踪自动统计信息更新?
· AI与.NET技术实操系列:使用Catalyst进行自然语言处理
· 分享一个我遇到过的“量子力学”级别的BUG。
阅读排行:
· C# 中比较实用的关键字,基础高频面试题!
· .NET 10 Preview 2 增强了 Blazor 和.NET MAUI
· 为什么AI教师难以实现
· 如何让低于1B参数的小型语言模型实现 100% 的准确率
· AI Agent爆火后,MCP协议为什么如此重要!
点击右上角即可分享
微信分享提示