diff options
Diffstat (limited to 'plugins/org.eclipse.mat.ui.help/concepts/heapdump.dita')
| -rw-r--r-- | plugins/org.eclipse.mat.ui.help/concepts/heapdump.dita | 18 |
1 files changed, 12 insertions, 6 deletions
diff --git a/plugins/org.eclipse.mat.ui.help/concepts/heapdump.dita b/plugins/org.eclipse.mat.ui.help/concepts/heapdump.dita index 0fe0a22d..176dbced 100644 --- a/plugins/org.eclipse.mat.ui.help/concepts/heapdump.dita +++ b/plugins/org.eclipse.mat.ui.help/concepts/heapdump.dita @@ -27,18 +27,18 @@ <conbody>
<p>A heap dump is a snapshot of the memory of a Java process at a certain point of time.
- There are different formats for persisting this data, and depending on the format it may
- contain different pieces of information, but in general the snapshot contains information
- about the java objects and classes in the heap at the moment the snapshot was triggered.
- Usually a full GC is triggered before the heap dump is written so it contains
+ There are different formats for persisting this data, and depending on the format, may
+ contain different pieces of information; but, in general, the snapshot contains information
+ about the Java objects and classes in the heap at the moment the snapshot was triggered.
+ In some cases, a full GC is triggered before the heap dump is written so it contains
information about the remaining objects.</p>
<p>The Memory Analyzer is able to work with HPROF binary heap dumps,
- IBM system dumps (after preprocessing them), and IBM portable heap dumps (PHD)
+ IBM system dumps (old versions require preprocessing), and IBM portable heap dumps (PHD)
from a variety of platforms.
</p>
<p>
- Typical information which can be found in heap dumps (once more - depending on the heap dump type) is:
+ Typical information which can be found in heap dumps (depending on the heap dump type):
</p>
<ul>
@@ -49,6 +49,12 @@ <li>
All Classes
<p>Classloader, name, super class, static fields</p>
+ <p>When MAT parses IBM system dumps, the size of classes includes some of the amount
+ of native memory in the Java process (but outside of the Java heap) which is related
+ to those classes such as native memory for bytecode and JIT compiled code for the class
+ methods. In some cases, this may cause the total size reported on the Overview pane to
+ exceed the maximum Java heap size. This calculation may be disabled using an option
+ in the MAT configuration.</p>
</li>
<li>
Garbage Collection Roots
|