Submitted On 08-NOV-2007
Still happening with 1.6.0_05-ea-b06, again *only* with the server VM.
Submitted On 19-DEC-2007
Still happening with 1.6.0_10-ea-b08, again *only* when specifying "-server".
Submitted On 25-DEC-2007
Same still happens with Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b09 mixed mode linux-amd64)
Submitted On 25-DEC-2007
Current CompileTask:
C2:1817 org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith([Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;Lorg/eclipse/core/internal/dtree/IComparator;)[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode; (469 bytes)
Submitted On 13-JAN-2008
Also happens with the just released 1.6.0.04
Submitted On 13-JAN-2008
A workaround is to exclude the method from compilation:
~/dev/eclipse$ cat .hotspot_compiler
exclude org/eclipse/core/internal/dtree/DataTreeNode forwardDeltaWith
Submitted On 13-JAN-2008
This issue comes and goes, but has been there for year or more.
Submitted On 15-JAN-2008
kutzi
This is really bad. I get it with 1.6.0_04 server VM and Eclipse 3.3.1.1 on a 64 Bit Linux as well as on Windows XP 32-Bit
I can reproduce it quite easily by fiddling with the build path. I.e. adding or removing source folder or jars
Submitted On 15-JAN-2008
It seems that this time excluding the method from being compiled doesn't help:
So:
jarkko@azkaban:~/dev/jee/eclipse$ ./eclipse
CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith
still causes exactly the same error as without it (64bit linux with -server).
Current CompileTask:
C2:1257 org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith([Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;Lorg/eclipse/core/internal/dtree/IComparator;)[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode; (469 bytes)
Submitted On 16-JAN-2008
jarkko23
Also happens in Linux with JDK 1.6.0_04 64bit and client hotspot.
Submitted On 16-JAN-2008
kutzi
@jarkko23: I think that's because on 64-Bit Linux there is no server VM. I.e. even if you start with -client you get a server VM.
Check your java.vm.name!
Submitted On 16-JAN-2008
kutzi
@jarkko23: I think that's because on 64-Bit Linux there is no client VM. I.e. even if you start with -client you get a server VM.
Check your java.vm.name!
Submitted On 28-JAN-2008
jackass2600
just another me too -- I get this error running eclipse 3.3.1.1 on winXp(32-bit). It started happening when I went from 1.6.0_03 to 1.6.0_04 and only happens with -server (switched to -client and everything is fine). There is no way I'm running eclipse with -Xint :-)
Submitted On 03-FEB-2008
hubick
I'm also seeing this on my Fedora 8 x86_64 box with eclipse.buildId=M20071023-1652:
# SIGSEGV (0xb) at pc=0x00002aaaaacc1fa1, pid=2973, tid=1083214160
# Java VM: IcedTea 64-Bit Server VM (1.7.0-b21 mixed mode linux-amd64)
# Problematic frame:
# V [libjvm.so+0x205fa1]
Submitted On 04-FEB-2008
Crashed also on RHEL5 Linux 2.6.18-8.el5 & Eclipse 3.3.1 & 1.6.0_04-b12 Sun server VM. Staring with -client helps.
Submitted On 13-FEB-2008
Faux
Duplicated with Eclipse x64 I20080207-1530:
OS: Windows Vista Build 6000
CPU:total 4 (4 cores per cpu, 1 threads per core) family 6 model 15 stepping 11, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3
Memory: 4k page, physical 8386880k(5578272k free), swap 16789432k(12674920k free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (10.0-b19) for windows-amd64 JRE (1.6.0_04-b12), built on Dec 14 2007 00:44:23 by "java_re" with MS VC++ 8.0
Submitted On 14-FEB-2008
Same problem on Red Hat enterprise 4 x86-64 box running Tomcat and Fedora 8 x86-64 running Eclipse. The problem is easy to reproduce by opening editors in Eclipse.
Submitted On 14-FEB-2008
above comment using 1.6.0_04 release build
Submitted On 24-FEB-2008
dlaur
Another me too.
I run into this with 1.6.0_04 running eclipse on a 64-bit redhat fedora 8 system. I have no problems with 1.6.0._03 (which is what I guess I will continue running until this gets resolved)
Submitted On 28-FEB-2008
ksucamk
I can reproduce this pretty often on 64-bit linux with eclipse. Here's the bad assert in hotspot output from 1.7.0 b24 fastdebug:
# Internal Error (/BUILD_AREA/jdk7/hotspot/src/share/vm/opto/coalesce.cpp:109), pid=17441, tid=1084725584
# Error: assert(src,"")
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (12.0-b01-fastdebug mixed mode linux-amd64)
Current CompileTask:
C2:1755 org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith([Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;Lorg/eclipse/core/internal/dtree/IComparator;)[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode; (469 bytes)
Submitted On 06-MAR-2008
kutzi73
Still not fixed in 1.6.0_05 release?
This is pretty bad as it basically prevents one from running Eclipse on a 64-bit system
Submitted On 06-MAR-2008
fw@deneb.enyo.de
Here's a backtrace from the crash with jdk-7-ea-bin-b24-linux-amd64-debug-04_dec_2007.jar (I've got a core file, too). I can reproduce this issue in my Eclipse workspace if I perform certain actions, but my attempts at reducing the workspace to a minimal set of classes/projects have failed.
#0 0x00002b84d4a83ee5 in raise () from /lib/libc.so.6
#1 0x00002b84d4a85403 in abort () from /lib/libc.so.6
#2 0x00002b84d557910e in os::abort () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#3 0x00002b84d57568b5 in VMError::report_and_die () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#4 0x00002b84d5180fae in report_assertion_failure () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#5 0x00002b84d50f5faa in PhaseChaitin::Union () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#6 0x00002b84d50f6984 in PhaseCoalesce::combine_these_two () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#7 0x00002b84d50f84f3 in PhaseAggressiveCoalesce::coalesce () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#8 0x00002b84d50f6a91 in PhaseCoalesce::coalesce_driver () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#9 0x00002b84d507c760 in PhaseChaitin::Register_Allocate () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#10 0x00002b84d51230ca in Compile::Code_Gen () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#11 0x00002b84d511d109 in Compile::Compile () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#12 0x00002b84d505b6c0 in C2Compiler::compile_method () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#13 0x00002b84d512c939 in CompileBroker::invoke_compiler_on_method () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#14 0x00002b84d512bdab in CompileBroker::compiler_thread_loop () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#15 0x00002b84d56fa4e3 in compiler_thread_entry () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#16 0x00002b84d56f08f5 in JavaThread::thread_main_inner () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#17 0x00002b84d56f07bd in JavaThread::run () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#18 0x00002b84d557e9ed in java_start () from /tmp/jdk1.7.0/fastdebug/jre/lib/amd64/server/libjvm.so
#19 0x00002b84d451ffc7 in start_thread () from /lib/libpthread.so.0
#20 0x00002b84d4b2129d in clone () from /lib/libc.so.6
Submitted On 07-MAR-2008
PeterHendriks
Same problem, Eclipse 3.3.2, Windows XP SP2 32-bit
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Server VM (build 10.0-b19, mixed mode)
Added the following to eclipse.ini: -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
As a workaround. Other workaround is not using server vm.
Submitted On 20-MAR-2008
Hey My Friend,
I also encounter this problem during executing "eclipse".
My Platform are CentOS 5.1 i386/x86_64.
Regards,
Simon
Submitted On 11-APR-2008
rgunther
Same problem under CentOS 4.6, jdk1.6.0_05, Eclipse 3.4M5. This bug is a serious issue for us.
Submitted On 15-APR-2008
reproduced with Windows Vista 64, eclipse 3.4M6 x64
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b11 mixed mode windows-amd64)
Submitted On 10-MAY-2008
Same problem here, with Eclipse 3.3.2 on Debian Lenny amd64 (future Debian 5.0) using Sun JVM 1.6.0_05.
It appeared when I installed the Maven Integration plugin... and/or when I started adding big Java projects to the workspace. It specifically triggers on heavy background compilations, for example after deleting a project from the WS so it has to recompile everything.
I tried increasing the perm size but that didn't work. The .hotspot_compiler trick didn't work either.
But it DID work this: (thanks PeterHendriks!)
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
to eclipse.ini below the -XX:MaxPermSize=256m setting
It's too bad this bug is still present in 1.6.0_10 and in the jdk7 as the other comments suggest.
It's also bad the jdk is Server only - Eclipse startup takes ages.
Submitted On 16-MAY-2008
I am told by the Eclipse team this is also my problem. Running Eclipse 3.4M7 on Windows Vista x86_64 SP1
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000008093dab, pid=184, tid=292
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b22 mixed mode windows-amd64)
# Problematic frame:
# V [jvm.dll+0x93dab]
fixed with:
C:\Program Files\eclipse-M7>echo exclude org/eclipse/core/internal/dtree/DataTre
eNode forwardDeltaWith > .hotspot_compiler
Submitted On 20-MAY-2008
This build DOES NOT solve this issue for me in Eclipse.
Java(TM) SE Runtime Environment (build 1.6.0_10-beta-b24)
Java HotSpot(TM) 64-Bit Server VM (build 11.0-b12, mixed mode)
I have to continue to use the hotspot JIT exclusion otherwise Eclipse crashes instantly when I modify my project classpath:
C:\Program Files\eclipse-M7>echo exclude org/eclipse/core/internal/dtree/DataTreeNode forwardDeltaWith > .hotspot_compiler
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006da2d2d0, pid=2976, tid=5296
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b12 mixed mode windows-amd64)
# Problematic frame:
# V [jvm.dll+0x30d2d0]
And why has the bug with fewer votes been promoted? It is bad form to have the word "Eclipse" listed on the top bug counts? Conspiratorial? Please say no... just fix it (really fix it).
Submitted On 26-MAY-2008
okrische
Same problems here with CompilerThread, Ubuntu 64bit and eclipse.
Happens lately also in a different region, after excluding the forwardDelta-Method:
Complete log is here:
http://www.ecopatz.de/hs_err_pid8643.log
Or a cut from it:
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b11 mixed mode linux-amd64)
# Problematic frame:
# V [libjvm.so+0x4d3040]
...
Current CompileTask:
C2:2599 org.eclipse.jdt.internal.compiler.lookup.ParameterizedMethodBinding.<init>(Lorg/eclipse/jdt/internal/compiler/lookup/ParameterizedTypeBinding;Lorg/eclipse/jdt/internal/compiler/lookup/MethodBinding;)V (435 bytes)
Submitted On 29-MAY-2008
Olaf_Geibig
I had the same crash today based on the ParameterizedMethodBinding class. Now I got around both issues by excluding these instructions:
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
-XX:CompileCommand=exclude,org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding,<init>
But that is really very ugly. Please fix it.
Cheers, Olaf
Submitted On 09-JUN-2008
aph
Patch at http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2008-June/000207.html
Submitted On 26-JUN-2008
mauromol
This bug is marked as fixed and delivered for "hs11" and "hs13"... what does this mean? The problem is still present in 1.6.0u6!
Thanks,
Mauro.
Submitted On 08-JUL-2008
Is there any hope of this fix being pushed out in a 6u7 update SOON? Making Eclipse unusable without complex workaround options is a big deal, and deserves to be rectified.
Submitted On 11-JUL-2008
kutzi73
With JRE 6u5-p I regularly got an VM crash in org.eclipse.jdt.internal.core.PackageFragmentRoot.computeFolderChildren (Eclipse 3.4).
"
Current CompileTask:
C2:1654 ! org.eclipse.jdt.internal.core.PackageFragmentRoot.computeFolderChildren(Lorg/eclipse/core/resources/ICon
tainer;Z[Ljava/lang/String;Ljava/util/ArrayList;[[C[[C)V (292 bytes)
"
After excluding the method with -XX:CompileCommand it seems to be fine.
Is this related to this bug?
Submitted On 17-JUL-2008
davide_cavestro
The problem still persists on "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
Does this mean that we'll never see a fix on HotSpot 10 / Java 6?
Submitted On 21-JUL-2008
kutzi
Davide, if I understand the "Release Fixed" field right, this will be fixed in Java 6 in Bug 2164190.
Submitted On 23-JUL-2008
duckconfit
This happens to me on Centos 5.0 on Intel Xeon 64bit machines with update 7. Update 3 runs without issue but as soon as I tried out update 7, I would keep getting this crash.
Submitted On 24-JUL-2008
ijuma82
For those who are unsure, there are 3 ways to get this fix:
- Use OpenJDK6 build 11 or later.
- Use JDK 6 Update 10 build 27 or later (download it from here http://download.java.net/jdk6/binaries/)
- Use a recent JDK7 snapshot (OpenJDK or otherwise).
Hope this helps.
Submitted On 13-AUG-2008
Bug 2164815 is now reporting fix delivered in hotshot 10 b25 - finally some indication that this might possibly be fixed in 6u8, if it happens.
Submitted On 16-AUG-2008
MartinHilpert
Same damn crash with latest Eclipse 3.4 (Ganymede( and Sun JDK 1.6.0_07 on a 64 Bit Ubuntu 8.04 Linux:
Current CompileTask:
C2:1038 org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith([Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode;Lorg/eclipse/core/internal/dtree/IComparator;)[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode; (469 bytes)
Neither of the workarounds:
1.)
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
2.)
/apps/eclipse>echo exclude org/eclipse/core/internal/dtree/DataTreeNode forwardDeltaWith > .hotspot_compiler
work for me :-(
Submitted On 24-SEP-2008
rlhartley
Of the two workarounds:
1.)
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith
Doesn't work consistently for me.
2.)
/apps/eclipse>echo exclude org/eclipse/core/internal/dtree/DataTreeNode forwardDeltaWith > .hotspot_compiler
works for me, but *only* if the .hotspot_compiler is in the *current* directory when starting.
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
