RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 738674 - Oracle JDK 1.6.0_26 build 20.1-b02 (installed from the Oracle tarball) crashes with Segmentation Fault on 64-bit RHEL6.1
Summary: Oracle JDK 1.6.0_26 build 20.1-b02 (installed from the Oracle tarball) crashe...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.6.0-sun
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: jiri vanek
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-15 14:06 UTC by David Tonhofer
Modified: 2012-01-11 09:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-11 09:54:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description David Tonhofer 2011-09-15 14:06:29 UTC 
Description of problem:

(Super vague problem. I'm using this bug just as a hook; if more info, will add.)

Currently we only have:

"Oracle JDK 1.6.0_26 build 20.1-b02 (installed from the Oracle tarball) crashes with Segmentation Fault on 64-bit RHEL6.1"

How reproducible: Under load after an hour or so.
Comment 2 RHEL Program Management 2011-09-15 14:28:31 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 jiri vanek 2011-09-16 06:35:26 UTC 
Why are you using tarballed jdk except of RPMd one? 
Also you can try latest released oracle tarball - u27 - there are many "segmentation faults" fixes.

Can you provide some kind of reproducer? Then maybe we can fix it in openjdk or find jdk7 backport.
Comment 4 David Tonhofer 2011-09-20 09:47:29 UTC 
Thank you for the response.

> Why are you using tarballed jdk except of RPMd one? 

I like to have the stuff all under /usr/local/java, actually. The /opt hierarchy was a great idea IMHO.

Anyway - Cannot reproduce with confidence.

It seems to occur during a stack overflow - indeed deeply nested calls were being at the three crash times observed (which still had a size of -Xss=500k). One would expect a java.lang.StackOverflowError though.

I tried to get a dump file from the process but no joy - didn't get one even with "ulimit -c unlimited"; nor did I get one of the good old "hs_err" files. Are these switched on only with -XX:ErrorFile nowadays?

Added "-XX:ErrorFile=./hs_err_pid$$.log" (current directory writeable and all), so we will see.

Unfortunately this system needs to be stable, so upgraded to build 1.6.0_27-b07.

Currently rebuilding our test system, maybe I can get the crash back there.
Comment 5 David Tonhofer 2011-10-24 16:00:28 UTC 
No problem with build 1.6.0_27-b07.

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