openjdk team mailing list archive

[neiltait <neil.tait@xxxxxxxxxxxxxx>]

no joy with openjdk-6...

-- 
eclipse 3.3.2 crashes on project right-click on java-6-openjdk and java-6-sun, but not java-1.5.0-sun (Hardy regression - libxcb.so)
https://bugs.launchpad.net/bugs/217538
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.

Status in Source Package "openjdk-6" in Ubuntu: Incomplete

Bug description:
I can reliably reproduce this bug on Hardy with Eclipse 3.3.2, and confirm that this problem did not exist in Gutsy.

1. Set my java alternatives to java-6-openjdk or java-6-sun
2. Run my externally unpacked eclipse 3.3.2 install from /opt/eclipse
3. Wait for eclipse to finish loading
4. Right click on an open project in the workspace

Eclipse immediately terminates without any warning or explanation. This bug will appear at other times during eclipse usage that appear to be random (to me) but right-clicking on a project will crash eclipse without fail at any point during usage (always before the right-click menu even appears). There is no output in the .metadata/.log file where eclipse normally leaves crash info. 

If I run eclipse from the command line I get the following error at eclipse termination:

#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xb75eeeb5, pid=18270, tid=3074725664
#
# Java VM: OpenJDK Client VM (1.6.0-b08 mixed mode, sharing linux-x86)
# Problematic frame:
# C  [libxcb.so.1+0x7eb5]
#
# An error report file with more information is saved as:
# /opt/eclipse/hs_err_pid18270.log
#
# If you would like to submit a bug report, please visit:
#   https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)

I have attached the hs_err_pid18270.log file that the JVM dumped.

----

This bug does not manifest when running on the latest java-1.5.0-sun runtime.

Also, I previously experienced the "sloppy locking" problem relating to libxcb.so in other apps like Netbeans as well as Eclipse but it did not cause the application to crash like this. The "sloppy locking" issue has been fixed by recent updates, but this fatal eclipse issue remains (I cannot reproduce it with any other java application).