简体   繁体   English

VisualVM堆转储与事件探查器不一致

[英]VisualVM heap dump inconsistency with profiler

I am using VisualVM (Built in JDK1.6) to analyze my Java application looking for memory leaks. 我正在使用VisualVM(JDK1.6中内置)来分析我的Java应用程序以查找内存泄漏。 I am using Heap Dump and the Profiler ( memory monitor ) both VisualVM features... there is some inconsistency i cant understand, when dumping the heap i can see that there is a class which i wrote with about 8000 instance, when looking at the profiler classes & instances i cannot find the related class.. after a few heap dumps with period of time between i can see that the number of instances of the class is increasing and still in the profiler is gone. 我正在使用堆转储和探查器(内存监视器)这两个VisualVM功能...有一些我无法理解的不一致之处,当转储堆时,我可以看到有一个类是用大约8000个实例编写的,探查器类和实例,我找不到相关的类..经过一段时间之间的一段时间的堆堆转储后,我可以看到该类的实例数量在增加,但仍在探查器中消失了。

I am wonder if this class is leaking, and why i cant see that on the profiler monitor? 我想知道此类是否正在泄漏,为什么我无法在探查器监视器上看到它?

Thanks for the help. 谢谢您的帮助。

In VisualVM monitor is equivalent of heap dump. 在VisualVM中,监视器等效于堆转储。 Profiler show instances that was created from start of profiling session. Profiler显示从概要分析会话开始创建的实例。

But if you told that number of instances increasing they should go to profiler result. 但是,如果您告知实例数量增加,则应转到分析器结果中。 Strange. 奇怪。 This work for me. 这项工作对我来说。 Try other profiler. 尝试其他探查器。 I prefer YourKit. 我更喜欢YourKit。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM