JVM utterly unstable with Eclipse 3.2.2/3.3 on x86_64

Bug #206620 reported by Franck on 2008-03-25
This bug report is a duplicate of:  Bug #174759: Eclipse crashes due to jvm crash. Edit Remove
26
Affects Status Importance Assigned to Milestone
openjdk-6 (Ubuntu)
Undecided
Unassigned
Nominated for Hardy by Vittorio Ballestra
sun-java6 (Ubuntu)
Undecided
Unassigned
Nominated for Hardy by Vittorio Ballestra

Bug Description

Running stock (not packaged) Eclipse 3.2.2/3.3 from eclipse.org (eclipse-java-europa-winter-linux-gtk-x86_64.tar.gz)
is really unstable on my x86_64 laptop.

JVM crashes really often, with log file similar to the one attached.

Don't know what other information to provide to make the report usefull...

This seems to happen with sun-java-6 and openjdk alike.

Franck (alci) wrote :
Matti Lindell (mlind) wrote :

Does passing -XX:MaxPermSize=128M to jvm have any difference? You can put that in eclipse.ini.

Franck (alci) wrote :

No, it does not make any difference.

Still crashes in CompilerThread0 process...

Franck (alci) wrote :

Just a note to say I can reproduce the problem from scratch with the main project I work on.
Steps I follow are :

- download eclispe 3.3 from eclipse.org
- unzip
- run eclipse and create workspace
- install subclipse (subversion plugin)
- create project from svn repository
- add xercesImpl.jar to ant classpath
- clean / rebuild using ant
- press F5 to refresh the project
- ***crash***

from now on, eclipse will crash after a few a few seconds, with the very same error log (below some chosen part of it that are always the same, full log is already attached) :
....
# Problematic frame:
# V [libjvm.so+0x20afb0]
....
Current thread (0x00000000006b9000): JavaThread "CompilerThread1" daemon
....
Current CompileTask:
C2:350 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)

I can reproduce as well.

# Java VM: OpenJDK 64-Bit Server VM (1.6.0-b07 mixed mode linux-amd64)
# Problematic frame:
# V [libjvm.so+0x20afb0]

Current thread (0x00000000006b8c00): JavaThread "CompilerThread1" daemon [_thre
ad_in_native, id=9803, stack(0x00000000420a2000,0x00000000421a3000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000
000000000

Current CompileTask:
C2:831 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)

Full crash log also attached.

Should note that I had this issue before with:

# SIGSEGV (0xb) at pc=0x00007f59b254222a, pid=32446, tid=1105189200
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0-b19 mixed mode linux-amd64)
# Problematic frame:
# V [libjvm.so+0x1f122a]

So the issue is likely with the JDK itself. Full crash log from previous instance of crash inclueded as well. That was NOT on the OpenJDK but the sun-java version.

Work around same as last time, sudo update-java-alternatives -s java-1.5.0-sun

Franck (alci) wrote :

Other workaround is to switch to i386 architecture... there OpenJdk is stable with eclipse 3.3.

Matthias Klose (doko) wrote :

is this seen with the sun-java6-jre package as well?

Changed in openjdk-6:
status: New → Incomplete
Gabriel Bauman (gabrielbauman) wrote :

I'm getting this with Eclipse 3.2.2 as packaged with hardy as well, again with openjdk-6. Attaching an example trace.

Gabriel Bauman (gabrielbauman) wrote :
Gabriel Bauman (gabrielbauman) wrote :
Gabriel Bauman (gabrielbauman) wrote :
Gabriel Bauman (gabrielbauman) wrote :
Gabriel Bauman (gabrielbauman) wrote :

This is reproducible on multiple systems. Setting confirmed to avoid the Janitor.

Changed in openjdk-6:
status: Incomplete → Confirmed
Gabriel Bauman (gabrielbauman) wrote :

Same crash with sun-java6.

exactt (giesbert) wrote :

setting to confirmed for sun-java6 as well as i also get the [libjvm.so+0x1f122a] error. tested with latest hardy x86_64.

description: updated
Changed in sun-java6:
status: New → Confirmed

SAME On 32 bit architectures. here's my log. Eclipse is unusable. Actually this is true also using sun jdk. Methink the problem is with new glibc because this eclipse began crashing after switching to hardy beta.

Stephen Eilert (outworlder) wrote :

I can confirm the crash on Hardy I386.

The crash happens with sun-java-6 and openjdk-6, but not with sun-java-5.

I'm inclined to agree with Vittorio. I get the same problem with Hardy using an x64 JDK downloaded directly from Sun (1.6.0_06).

Eric Buist (buisteric) wrote :

So, AGAIN, there is nothing to do for that too??? This is a very very bad problem; I cannot work at all this way. Eclipse crashes right after I open and compile my project, even if I try with Ubuntu Eclipse, or eclipse.org's version. I tried with Sun's JDK 6 and OpenJDK 6 without any success. The only working combination was 32-bits Eclipse, 32-bits Sun's JVM 6, but I cannot access CVS with that; it refuses to connect to Internet. So the only solution is to downgrade to Gutsy, but I find this very LONG and annoying.

Nicolas Albert (nicoa380) wrote :

@Eric Buist :
don't downgrade all your system to Gutsy, just the jdk !
- remove all your sun-* and openjdk package
- download package from gutsy :
goto http://archive.ubuntu.com/ubuntu/pool/multiverse/s/sun-java6/
and download all 6-03-0ubuntu2 package for your computeur ( i386 or amd64 + all ) in a folder (~/jdk ?)
- install them :
dpkg -i ~/jdk/*.deb
- lock the version in synaptic (or what you what) and that all !

branflake2267 (branflake2267) wrote :

Setting 'JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun' in ~/.eclipse/eclipserc fixed it for me.

I tried OpenJDK and got the crash, I tried sun-java-6 and got the crash on my Ubuntu 8.04 hardy amd x64 system. Started happening after the upgrade. Very annoying bug.

mark (markrmiller) wrote :

Best fix that worked for me (so far) is from the other issue that this is a dupe of:

 add to eclipse.ini:
  -XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith

Cleared up my frequent crashing. Really a pain to have to deal with Eclipse when its crashing every 2 min:)

Markus Majer (mpathy) wrote :

Use sun-java-5 to start eclipse. There it runs stable.
You can do your projects in sun-java-6 or OpenJDK as you want.

Pkapsc (andre-pietsch) wrote :

"-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/DataTreeNode,forwardDeltaWith"
This did not work for me.
Ubuntu 8.0.4
2.6.24-17-generic
java-1.5.0-sun-1.5.0.15

branflake2267's solution worked for me as well. This seems the most straight-forward solution:

>>>> branflake2267 wrote on 2008-04-29: (permalink)
>>>>
>>>> Setting 'JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun' in ~/.eclipse/eclipserc fixed it for me.
>>>>
>>>> I tried OpenJDK and got the crash, I tried sun-java-6 and got the crash on my Ubuntu 8.04 hardy amd x64 system. Started happening after the upgrade. Very annoying bug.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers