Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "MemoryAnalyzer/FAQ"

m (Frequently Asked Questions)
m (Problems Getting Heap Dumps)
Line 1: Line 1:
 
= Frequently Asked Questions =
 
= Frequently Asked Questions =
 
[[MemoryAnalyzer]], [http://www.eclipse.org/mat Home Page], [http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.memory-analyzer Forum]
 
[[MemoryAnalyzer]], [http://www.eclipse.org/mat Home Page], [http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.memory-analyzer Forum]
 +
 +
== Problems Starting the Memory Analyzer ==
 +
 +
=== java.lang.RuntimeException: No application id has been found. ===
 +
 +
The Memory Analyzer needs a '''Java 1.5''' VM to run (of course, heap dumps from JDK 1.4.2_12 on are supported).
 +
If in doubt, provide the runtime VM on the command line:
 +
<blockquote>MemoryAnalyzer.exe -vm &lt;path to 1.5 vm&gt;</blockquote>
  
 
== Problems Getting Heap Dumps ==
 
== Problems Getting Heap Dumps ==

Revision as of 07:50, 28 May 2008

Frequently Asked Questions

MemoryAnalyzer, Home Page, Forum

Problems Starting the Memory Analyzer

java.lang.RuntimeException: No application id has been found.

The Memory Analyzer needs a Java 1.5 VM to run (of course, heap dumps from JDK 1.4.2_12 on are supported). If in doubt, provide the runtime VM on the command line:

MemoryAnalyzer.exe -vm <path to 1.5 vm>

Problems Getting Heap Dumps

Error: Found instance segment but expected class segment

This error indicates an inconsistent heap dump: The data in the heap dump is written in various segments. In this case, an address expected in a class segment is written into a instance segment.

The problem has been reported in heap dumps generated by jmap on Linux and Solaris operation systems and jdk1.5.0_13 and below. Solution: use latest jdk/jmap version or use jconsole to write the heap dump (needs jdk6).

Error: Invalid heap dump file. Unsupported segment type 0 at position XZY

This almost always means the heap dumps has not been written properly by the Virtual Machine. The Memory Analyzer is not able to read the heap dump.

If you are able to read the dump with other tools, please file a bug report.

Back to the top