我尝试了很多方法，并将-VM参数放在建议的位置。但这行不通。最后我找到了解决办法。在执行任何插件或jar之前，vm args应该放在eclipse.ini文件中。我尝试了ubuntu 18.04中最新的eclipse [Photon]，它非常适合我。

-startup
-vm        
/usr/local/java/jdk1.8.0_251/bin/java.exe
plugins/org.eclipse.equinox.launcher_1.5.700.v20200207-2156.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.1100.v20190907-0426
-product
org.eclipse.epp.package.jee.product
-showsplash
org.eclipse.epp.package.common
--launcher.defaultAction
openFile
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=@user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
--add-modules=ALL-SYSTEM
-Dosgi.requiredJavaVersion=1.8
-Dosgi.dataAreaRequiresExplicitInit=true
-Xms256m
-Xmx2048m
--add-modules=ALL-SYSTEM

刚刚卸载了jre-32位版本，它对我来说工作得很好。

在我的案例中，JAVA路径没有在Env变量中设置。在Env path中设置正确路径后开始工作。

在命令提示符中输入javac，并确保JAVA PATH正确。

1)打开SpringToolSuite4.ini文件。 2)在SpringToolSuite4.ini文件中搜索“openFile”文本。 3)在SpringToolSuite4.ini中提供javaw.exe文件位置 4)注意:提供-vm和你的javaw.exe文件路径之间的新行，如下所示。

openFile 虚拟机 C:\Program Files\Java\jdk1.8.0\bin\javaw.exe —vmargs -Dosgi.requiredJavaVersion = 1.8 -Xms256m

In my opinion the most answers here regarding different architectures of Eclipse and Java are simply wrong and this can be easily checked using e.g. Process Monitor under Windows. The -vm option is there to run a specific version of java and the point of it is, that the configured process is started and runs all the Java code on its own, that's why you configure up to java.exe. In that case you DON'T need to have the same architecture for Eclipse and Java, but can happily mix both 32 Bit and 64 Bit. You only CAN'T mix both, if you DON'T use -vm, but let Eclipse load Java natively into its own process using jvm.dll and such. That latter behavior is Eclipse's default, but not the case anymore if you properly configure -vm in eclipse.ini.

如果你不相信我，你可以自己用Eclipse和Java的不同体系结构做一些测试，并正确地配置-vm。最后，这正是提问者在对公认答案的评论中所描述的:

不能运行Eclipse;JVM终止。退出代码= 13

他说64位JDK现在正在工作，但在他的截图中可以看到他的Eclipse是32位的，因为启动器的路径。库是32位的。

And now for the reason I came here: Ony of my customers had some problems loading one of our Eclipse/OSGI based applications as well and Java exited with exit code 13. In the end it showed that the problem was not about -vm or the architectures of Java and eclipse.exe, but instead he was simply missing config.ini and I guess eclipse.exe wasn't aware what to load or such. After we recognized that and put a config.iniback in place, the app loaded fine with using -vm and a 64 Bit JRE7 in combination with a 32 Bit eclipse.exe.

我刚遇到同样的问题，花了大约一个小时来解决这个问题。 最后它是路径中的“#”字符。

因此，我将“C:\# IDE\eclipse 3.7\”重命名为“C: + IDE\eclipse 3.7\”，这就解决了问题。