{"componentChunkName":"component---src-templates-post-template-js","path":"/note-eclips-mat-setup-en","result":{"data":{"markdownRemark":{"id":"f74b0156-5aad-59e8-8338-ee1624f8247a","html":"<blockquote>\n<p>This page has been machine-translated from the <a href=\"/note-eclips-mat-setup\">original page</a>.</p>\n</blockquote>\n<p>When installing Eclipse Memory Analyzer, which is useful for analyzing Java VM dump files (<code class=\"language-text\">.hprof</code>), I ran into the <code class=\"language-text\">version 1.8.0_261 of the jvm is not suitable</code> error. This article summarizes how to fix it.</p>\n<p>First, download the standalone binary of Eclipse Memory Analyzer from the link below.</p>\n<p>Reference: <a href=\"https://www.eclipse.org/mat/downloads.php\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Eclipse Memory Analyzer Open Source Project | The Eclipse Foundation</a></p>\n<p>Next, download a version of Java that satisfies the dependency requirements.\nThis time, I downloaded Java 17 from the source below.</p>\n<p>Reference: <a href=\"https://www.oracle.com/java/technologies/downloads/#java17\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Java Downloads | Oracle</a></p>\n<p>After running the downloaded installer, the files were extracted to <code class=\"language-text\">C:\\Program Files\\Java\\jdk-17\\</code>.</p>\n<p>Next, extract the downloaded Eclipse Memory Analyzer and add the following lines to <code class=\"language-text\">MemoryAnalyzer.ini</code>.</p>\n<div class=\"gatsby-highlight\" data-language=\"bash\"><pre class=\"language-bash\"><code class=\"language-bash\">-vm\nC:<span class=\"token punctuation\">\\</span>Program Files<span class=\"token punctuation\">\\</span>Java<span class=\"token punctuation\">\\</span>jdk-17<span class=\"token punctuation\">\\</span>bin<span class=\"token punctuation\">\\</span>javaw.exe</code></pre></div>\n<p>This lets you specify Java 17 as the Java version used by Eclipse Memory Analyzer and avoid the <code class=\"language-text\">version 1.8.0_261 of the jvm is not suitable</code> error.</p>\n<p>The updated <code class=\"language-text\">MemoryAnalyzer.ini</code> looked like this.</p>\n<div class=\"gatsby-highlight\" data-language=\"bash\"><pre class=\"language-bash\"><code class=\"language-bash\"><span class=\"token comment\"># MemoryAnalyzer.ini</span>\n-startup\nplugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar\n--launcher.library\nplugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.2.700.v20221108-1024\n-vm\nC:<span class=\"token punctuation\">\\</span>Program Files<span class=\"token punctuation\">\\</span>Java<span class=\"token punctuation\">\\</span>jdk-17<span class=\"token punctuation\">\\</span>bin<span class=\"token punctuation\">\\</span>javaw.exe\n-vmargs\n--add-exports<span class=\"token operator\">=</span>java.base/jdk.internal.org.objectweb.asm<span class=\"token operator\">=</span>ALL-UNNAMED\n-Xmx1024m</code></pre></div>\n<p>After that, I was able to start <code class=\"language-text\">MemoryAnalyzer.exe</code>.</p>","fields":{"slug":"/note-eclips-mat-setup-en","tagSlugs":["/tag/notes/","/tag/memo/","/tag/english/"]},"frontmatter":{"date":"2023-05-17","description":"This article summarizes how to fix the `version 1.8.0_261 of the jvm is not suitable` error that appears when launching Eclipse Memory Analyzer as a standalone binary.","tags":["Notes","Memo","English"],"title":"How to Fix the `version 1.8.0_261 of the jvm is not suitable` Error When Launching Eclipse Memory Analyzer as a Standalone Binary","socialImage":{"publicURL":"/static/f31d0ca87e96fa11e3914121a9f8c781/note-eclips-mat-setup.png"}}}},"pageContext":{"slug":"/note-eclips-mat-setup-en"}},"staticQueryHashes":["251939775","401334301","825871152"]}