Note sure if its a java or eclipse bug.
I am not using the eclipse package from the ubuntu repository either.
That crash happens for me when auto-completion is used.
Like "System.out." and waiting for the possibilites, then very often (not always) eclipse crashes.
I used the reduced report since the full one had a size of over 600mb
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 2 20:12:09 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
NonfreeKernelModules: nvidia
Package: openjdk-6-jre-headless 6b18~pre1-1ubuntu1
ProcCmdline: /usr/bin/java -Dosgi.requiredJavaVersion=1.5 -XX:MaxPermSize=256m -Xms40m -Xmx512m -jar /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher /opt/eclipse/eclipse -name Eclipse --launcher.library /opt/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.200.v20090519/eclipse_1206.so -startup /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar -exitdata 238011 -product org.eclipse.epp.package.jee.product -vm /usr/bin/java -vmargs -Dosgi.requiredJavaVersion=1.5 -XX:MaxPermSize=256m -Xms40m -Xmx512m -jar /opt/eclipse//plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
ProcEnviron:
LANG=de_DE.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Signal: 5
SourcePackage: openjdk-6
StacktraceTop:
?? () from /usr/lib/libgdk-x11-2.0.so.0
_XError () from /usr/lib/libX11.so.6
?? () from /usr/lib/libX11.so.6
_XReply () from /usr/lib/libX11.so.6
XQueryPointer () from /usr/lib/libX11.so.6
Title: java crashed with signal 5 in _XError()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: admin
Maybe I was a bit hasty this bug matches the one I have like glove. However this one: https:/
Not sure about the right nomenclatue, but I'm pretty confident that this is not a java/eclipse bug per se. It happens with Sun's jdk versions u16 and u18 and with latest open-jdk
And it started to happen suddenly on Lucid after a routine update. It can of course be that change in X/Gtk stack have revealed a bug in java/eclipse, but it can be also the other way round.