Eclipse和Intellij不断因EXCEPTION_ACCESS_VIOLATION而崩溃

Question

更新：Intellij中似乎也出现了相同的问题。 我的Eclipse安装不断崩溃而没有警告。 该窗口将在随机点突然关闭。

有时会生成错误日志。 下面是一个示例（消息有所不同）

在Eclipse安装过程中，我遇到了一些崩溃问题。 我已经重新安装了Java（8）和Eclipse，甚至进行了全新的Windows安装（这只是更改了错误消息）

# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000003bd0248, pid=3780, tid=0x0000000000000718
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J 8164 C1 org.eclipse.emf.ecore.util.EcoreUtil$Copier.copy(Lorg/eclipse/emf/ecore/EObject;)Lorg/eclipse/emf/ecore/EObject; (139 bytes) @ 0x0000000003bd0248 [0x0000000003bcf3c0+0xe88]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x00000000025d0800):  JavaThread "main" [_thread_in_Java, id=1816, stack(0x0000000000050000,0x0000000000150000)]

siginfo: ExceptionCode=0xc0000005, reading address 0x00000000000003c1

Registers:
RAX=0x0000000000000000, RBX=0x000000001dd15fb8, RCX=0x000000000000047d, RDX=0x00000001003ae698
RSP=0x000000000014df30, RBP=0x000000001f727c40, RSI=0x00000000c1668a48, RDI=0x0000000000000001
R8 =0x000000001f727c40, R9 =0x0000000000000320, R10=0x0000000000000000, R11=0x0000000000000000
R12=0x0000000000000000, R13=0x000000010038d100, R14=0x000000000014de18, R15=0x00000000025d0800
RIP=0x0000000003bd0248, EFLAGS=0x0000000000010212

还有一个：

# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006ce0c220, pid=7156, tid=0x00000000000015a0
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [MSVCR100.dll+0x3c220]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x0000000017f4b000):  JavaThread "C1 CompilerThread1" daemon [_thread_in_vm, id=5536, stack(0x00000000189d0000,0x0000000018ad0000)]

siginfo: ExceptionCode=0xc0000005, reading address 0x000000002234fff8

Registers:
RAX=0x0000000000000027, RBX=0x0000000018acf968, RCX=0x000000002eca5910, RDX=0xfffffffff36aa6f0
RSP=0x0000000018aced48, RBP=0x00000000005aff00, RSI=0x000000001cd1fdc0, RDI=0x0000000021e25640
R8 =0x000000000052af00, R9 =0x0000000021fe9c00, R10=0x0000000000002000, R11=0x000000002e77b050
R12=0x00000000005aff00, R13=0x00000000000000b8, R14=0x000000001cd1fb70, R15=0x0000000000000000
RIP=0x000000006ce0c220, EFLAGS=0x0000000000010206

系统信息包含

---------------  S Y S T E M  ---------------

OS: Windows 10.0 , 64 bit Build 15063 (10.0.15063.0)

CPU:total 3 (3 cores per cpu, 1 threads per core) family 16 model 5 stepping 3, cmov, cx8, fxsr, mmx, sse, sse2, sse3, popcnt, mmxext, 3dnowpref, lzcnt, sse4a, tsc, tscinvbit, tscinv

Memory: 4k page, physical 8386740k(6510284k free), swap 10352820k(8395928k free)

vm_info: Java HotSpot(TM) 64-Bit Server VM (25.121-b13) for windows-amd64 JRE (1.8.0_121-b13), built on Dec 12 2016 18:21:36 by "java_re" with MS VC++ 10.0 (VS2010)

还有三分之一

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ILLEGAL_INSTRUCTION (0xc000001d) at pc=0x000000000276703f, pid=11876, tid=0x0000000000002e68
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J 32 C1 sun.misc.FDBigInteger.trimLeadingZeros()V (57 bytes) @ 0x000000000276703f [0x0000000002766f00+0x13f]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

工作区日志包含重复的内容：

!ENTRY org.eclipse.egit.ui 2 0 2017-04-11 18:19:39.359
!MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
user global configuration and to define the default location to store repositories: 'C:\Users\gardi'. If this is
not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
EGit might behave differently since they see different configuration options.
This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
!SESSION 2017-04-11 18:40:15.939 -----------------------------------------------
eclipse.buildId=4.6.3.M20170301-0400
java.version=1.8.0_121
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product

!ENTRY org.eclipse.egit.ui 2 0 2017-04-11 18:40:39.941
!MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
user global configuration and to define the default location to store repositories: 'C:\Users\gardi'. If this is
not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
EGit might behave differently since they see different configuration options.
This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.

eclipse.ini的内容

-startup
plugins/org.eclipse.equinox.launcher_1.3.201.v20161025-1711.jar
--launcher.library
C:\Users\gardi\.p2\pool\plugins\org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.401.v20161122-1740
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.8
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx1024m
-Declipse.p2.max.threads=10
-Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
-Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/

更新：尝试过Eclipse EXCEPTION_ACCESS_VIOLATION崩溃的解决方案，没有任何运气。

Answer 1

1. 检查/.metadata/.log并发布记录的消息
2. 导航到Eclipse工作区中名为.metadata的隐藏目录，将其删除并启动eclipse。 一旦Eclipse开始崩溃，.metadata目录中的文件似乎会引起反复出现的问题。

如果这样做没有帮助，请使用eclipse.ini文件包含的内容更新问题。