Bug 681903 - New Sun JDK needed to avoid Eclipse crashes when using CDT
Summary: New Sun JDK needed to avoid Eclipse crashes when using CDT
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.6.0-sun
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: jiri vanek
QA Contact: BaseOS QE - Apps
Depends On:
Blocks: GSS_6_2_PROPOSED 697582 705351 705353
TreeView+ depends on / blocked
Reported: 2011-03-03 14:49 UTC by Alan Matsuoka
Modified: 2018-11-14 14:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 705351 705353 (view as bug list)
Last Closed: 2011-05-30 08:46:34 UTC
Target Upstream Version:

Attachments (Terms of Use)
hs_err_pid10684.log (89.72 KB, text/x-log)
2011-03-03 14:52 UTC, Alan Matsuoka
no flags Details
sosreport-nkumar.00427426-20110225112752-8d61.tar.xz (2.29 MB, application/octet-stream)
2011-03-03 14:53 UTC, Alan Matsuoka
no flags Details
Reproduced for compressed oops issue (2.17 KB, application/octet-stream)
2011-03-03 16:19 UTC, Pavel Tisnovsky
no flags Details

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0835 normal SHIPPED_LIVE java-1.6.0-sun bug fix and enhancement update 2011-05-30 08:46:27 UTC

Description Alan Matsuoka 2011-03-03 14:49:50 UTC
Description of problem:
Eclipse crashes with Sun JDK when using CDT

When eclipse is loaded with a CDT project, it crashes the JVM when rebuilding the index. It seems this issue is caused due to Compressed Ordinary Object Pointers (Compressed Oops) being turned on in the newer Java HotSpot versions (update 23 onwards). With the update of Sun JDK packages in el6 to update 24, we are now running into this problem. FC14 had similar issues and it seems an updated eclipse package fixed the issue.


Can we get eclipse patched in el6 as well?

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Make sure java-1.6.0-sun- package is installed and is being used:

% rpm -qa | grep java-1.6.0-sun-

% update-alternatives --display java | grep -i link
 link currently points to /usr/lib/jvm/jre-1.6.0-sun.x86_64/bin/java

% java -version 
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)

2. Now run Eclipse (with CDT installed)
3. Create a C++ project
4. Add a main.cpp
5. add one line "#include <iostream>"
6. Save the file
7. If eclipse didn't crash right after saving, right click on the project and select Index->Rebuild Index

Actual results:

Eclipse crashes here with the following:

# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x00007f578c31889b, pid=10684, tid=140012374947584
# JRE version: 6.0_24-b07
# Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# j  org.eclipse.cdt.internal.core.dom.parser.cpp.semantics.CPPSemantics.declaredBefore(Ljava/lang/Object;Lorg/eclipse/cdt/core/dom/ast/IASTNode;Z)Z+15
# An error report file with more information is saved as:
# /home/fahome/nkumar/hs_err_pid10684.log
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp

Expected results:
Normal operation

Additional info:

This only happens with the Sun JDK.

Comment 1 Alan Matsuoka 2011-03-03 14:52:15 UTC
Created attachment 482100 [details]

Comment 2 Alan Matsuoka 2011-03-03 14:53:41 UTC
Created attachment 482101 [details]

Comment 3 Andrew Overholt 2011-03-03 16:09:15 UTC
This looks like bug #647737.  Can you try adding -XX:-UseCompressedOops to /etc/eclipse.ini?

Comment 4 Pavel Tisnovsky 2011-03-03 16:19:33 UTC
Created attachment 482115 [details]
Reproduced for compressed oops issue

Comment 5 Pavel Tisnovsky 2011-03-03 16:22:15 UTC
There's a reproduced for compressed oops issue stored in the attachment 482115 [details] (see comment #4). You can compile & run it to check if your JDK version has already compressed oops fix.

Comment 6 Andrew Overholt 2011-03-03 17:00:44 UTC
Do I just compile and run that test case?  I tried javac Test7002666.java; java Test7002666 with:

java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)

and got no errors.

Comment 7 Pavel Tisnovsky 2011-03-10 10:10:16 UTC
If the test does not fail it means you are using fixed IcedTea version.

Comment 8 Andrew Overholt 2011-03-11 20:27:26 UTC
(In reply to comment #7)
> If the test does not fail it means you are using fixed IcedTea version.

Does the version in comment #6 indicate that I am using the Sun JDK or the IcedTea version?  I thought it indicated Sun but I may be wrong.

Comment 9 Andrew Overholt 2011-05-16 17:00:11 UTC
I'm told this is fixed in newer versions of the Sun JDK so if we can get one of those into RHEL we'll be good to go and won't need to patch Eclipse to work around this JVM issue.

Re-assigning to the proper component.

Comment 13 errata-xmlrpc 2011-05-30 08:46:34 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.