Memory Analyzer 与 Java VM 版本支持问题

jvm内存快照dump文件太大，怎么分析_weixin_33921089的博客-CSDN博客
https://blog.csdn.net/weixin_33921089/article/details/94030868

Linux 中分析超大 JVM dump 文件 - 简书
https://www.jianshu.com/p/b3ed962b382c

jvm内存快照dump文件太大，怎么分析 - 神风炼 - 博客园
https://www.cnblogs.com/liangzs/p/8489321.html

linux下分析hprof大文件,hprof 分析工具_风雪轩的博客-CSDN博客
https://blog.csdn.net/weixin_36389909/article/details/116882121

Eclipse Memory Analyzer Open Source Project | The Eclipse Foundation
https://www.eclipse.org/mat/previousReleases.php

mat support jdk 1.8 - 国内版 Bing
https://cn.bing.com/search?q=mat+support+jdk+1.8&qs=n&form=QBRE&sp=-1&pq=mat+support+jdk+1.8&sc=0-19&sk=&cvid=D607E3993F0241BC83A12786F4F974E6

Eclipse Memory Analyzer Open Source Project | The Eclipse Foundation
https://www.eclipse.org/mat/

MemoryAnalyzer/FAQ - Eclipsepedia
https://wiki.eclipse.org/MemoryAnalyzer/FAQ

Frequently Asked Questions
MemoryAnalyzer, Home Page, Forum

Problems Starting the Memory Analyzer
java.lang.RuntimeException: No application id has been found.
Memory Analyzer 1.12 and later needs a Java 11 VM or later VM to run. **
The Memory Analyzer 1.8 to 1.11 needs a Java 1.8 VM or later 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/java8/bin>
Alternatively, edit the MemoryAnalyzer.ini to contain (on two lines):

-vm
path/to/java8/bin
(This error happens because the MAT plug-in requires a JDK 1.8 via its manifest.mf file and the OSGi runtime dutifully does not activate the plug-in.) Memory Analyzer version 1.1 will give a better error message pop-up.

Incompatible JVM
Version 1.4.2 of the JVM is not suitable for this product. Version 1.5.0 or greater is required.

Out of Memory Error while Running the Memory Analyzer
Well, analyzing big heap dumps can also require more heap space. Give it some more memory (possible by running on a 64-bit machine):

MemoryAnalyzer.exe -vmargs -Xmx4g -XX:-UseGCOverheadLimit
Alternatively, edit the MemoryAnalyzer.ini to contain:

-vmargs
-Xmx2g
-XX:-UseGCOverheadLimit
As a rough guide, Memory Analyzer itself needs 32 to 64 bytes for each object in the analyzed heap, so -Xmx2g might allow a heap dump containing 30 to 60 million objects to be analyzed. Memory Analyzer 1.3 using -Xmx58g has successfully analyzed a heap dump containing over 948 million objects.

The initial parse and generation of the dominator tree uses the most memory, so it can be useful to do the initial parse on a large machine, then copy the heap dump and index files to a more convenient machine for further analysis.

For more details, check out the section Running Eclipse in the Help Center. It also contains more details if you are running on Mac OS X.

If you are running the Memory Analyzer inside your Eclipse SDK, you need to edit the eclipse.ini file.

==========================================
MemoryAnalyzer/FAQ - Eclipsepedia

Problems Starting the Memory Analyzer
java.lang.RuntimeException: No application id has been found. or Incompatible JVM
Memory Analyzer 1.14 and later needs a Java 17 VM or later VM to run. Memory Analyzer 1.12 and later needs a Java 11 VM or later VM to run. The Memory Analyzer 1.8 to 1.11 needs a Java 1.8 VM or later 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/java17/bin
Alternatively, edit the MemoryAnalyzer.ini to contain (on two lines), and before any -vmargs lines:

-vm
path/to/java8/bin
(This error happens because the MAT plug-in requires a JDK 1.8 via its manifest.mf file and the OSGi runtime dutifully does not activate the plug-in.) Memory Analyzer version 1.1 will give a better error message pop-up.

Incompatible JVM
Version 1.4.2 of the JVM is not suitable for this product. Version 1.5.0 or greater is required.

or

Incompatible JVM
Version 11.0.17 of the JVM is not suitable for this product. Version 17 or greater is required.

/