Bug 677730

Summary: [abrt] java-1.6.0-openjdk-devel-1:1.6.0.0-52.1.9.6.fc14: os::abort: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Clemens Eisserer <linuxhippy>
Component: java-1.6.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ahughes, dbhole, jvanek, langel, lkundrak, mjw, mmatejov, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:62b6a4bb3fcbeacda16b9034fd470c81302e446f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:59:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
hotpost crash log eclipse 1
none
hotpost crash log eclipse 2
none
netbeans crash log
none
second stacktrace generated by abrt
none
1st hotspot crash file
none
2nd hotspot crash file
none
3rd hotspot crash file
none
4th hotspot crash file
none
5th hotspot crash file
none
crash right after starting eclipse none

Description Clemens Eisserer 2011-02-15 17:20:36 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 159260 bytes
cmdline: /usr/lib/jvm/java/bin/java -Djdk.home=/usr/lib/jvm/java -classpath /home/ce/Programme/netbeans-6.9.1/platform/lib/boot.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/org-openide-modules.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/org-openide-util.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/org-openide-util-lookup.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/boot_ja.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/boot_pt_BR.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/boot_zh_CN.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-modules_ja.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-modules_pt_BR.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-modules_zh_CN.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-util_ja.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-util-lookup_ja.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-util-lookup_pt_BR.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-util-lookup_zh_CN.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-util_pt_BR.jar:/home/ce/Programme/netbeans-6.9.1/platform/lib/locale/org-openide-util_zh_CN.jar:/usr/lib/jvm/java/lib/dt.jar:/usr/lib/jvm/java/lib/tools.jar -Dnetbeans.dirs=/home/ce/Programme/netbeans-6.9.1/nb:/home/ce/Programme/netbeans-6.9.1/ide:/home/ce/Programme/netbeans-6.9.1/java:/home/ce/Programme/netbeans-6.9.1/ergonomics:/home/ce/Programme/netbeans-6.9.1/bin/../xml:/home/ce/Programme/netbeans-6.9.1/apisupport:/home/ce/Programme/netbeans-6.9.1/bin/../webcommon:/home/ce/Programme/netbeans-6.9.1/websvccommon:/home/ce/Programme/netbeans-6.9.1/enterprise:/home/ce/Programme/netbeans-6.9.1/mobility:/home/ce/Programme/netbeans-6.9.1/profiler:/home/ce/Programme/netbeans-6.9.1/bin/../ruby:/home/ce/Programme/netbeans-6.9.1/bin/../python:/home/ce/Programme/netbeans-6.9.1/bin/../php:/home/ce/Programme/netbeans-6.9.1/bin/../visualweb:/home/ce/Pr
comment: Had that crashes also with Eclipse when running with CMS+ParNew but got no crash reports, switching to SerialGC solved it.
component: java-1.6.0-openjdk
Attached file: coredump, 901246976 bytes
crash_function: os::abort
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java
kernel: 2.6.35.11-83.fc14.i686
package: java-1.6.0-openjdk-devel-1:1.6.0.0-52.1.9.6.fc14
rating: 4
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/bin/java was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297776739
uid: 500

How to reproduce
-----
1. Started Netbeans with the CMS and ParNew garbage collector
2. While running idle in background, it suddenly crashed

Comment 1 Clemens Eisserer 2011-02-15 17:20:42 UTC
Created attachment 478926 [details]
File: backtrace

Comment 2 Clemens Eisserer 2011-02-15 17:22:48 UTC
Created attachment 478927 [details]
hotpost crash log eclipse 1

Comment 3 Clemens Eisserer 2011-02-15 17:23:33 UTC
Created attachment 478928 [details]
hotpost crash log eclipse 2

Comment 4 Clemens Eisserer 2011-02-15 17:24:17 UTC
Created attachment 478929 [details]
netbeans crash log

Comment 5 Clemens Eisserer 2011-02-15 17:24:59 UTC
Probably I should add I had no problems at all with this configuration (CMS+ParNew) on Fedora13's version of ideadtea.

Comment 6 Deepak Bhole 2011-02-15 17:36:52 UTC
Is this error reproducible for you? 

hs_err indicates a problematic compiled Java frame but the trace shows something different (error when iterating over oops of an oop during the mark phase).

Comment 7 Clemens Eisserer 2011-02-15 18:45:04 UTC
Yes, I get the error quite often when running eclipse/netbeans with CMS enabled - however its not triggered through any specific action.
Sometimes it occurs after a few minutes after starting the IDE, sometimes it takes several hours.

Comment 8 Deepak Bhole 2011-02-15 18:59:47 UTC
Do you have the trace from gdb for other runs by chance? If not, can you please file another abrt when it happens (so that it auto collects the trace), and link back to this one? It would be helpful to know if the error is always in that part of the code, or if it's a more ingrained GC bug that manifests in different ways..

Comment 9 Deepak Bhole 2011-04-11 18:32:19 UTC
Re-assigned by mistake. Assigning back to myself.

Comment 10 Clemens Eisserer 2011-05-12 08:27:08 UTC
Created attachment 498465 [details]
second stacktrace generated by abrt

Comment 11 Clemens Eisserer 2011-05-12 08:27:35 UTC
Created attachment 498466 [details]
1st hotspot crash file

Comment 12 Clemens Eisserer 2011-05-12 08:28:20 UTC
Created attachment 498467 [details]
2nd hotspot crash file

Comment 13 Clemens Eisserer 2011-05-12 08:28:48 UTC
Created attachment 498468 [details]
3rd hotspot crash file

Comment 14 Clemens Eisserer 2011-05-12 08:29:10 UTC
Created attachment 498469 [details]
4th hotspot crash file

Comment 15 Clemens Eisserer 2011-05-12 08:29:31 UTC
Created attachment 498470 [details]
5th hotspot crash file

Comment 16 Clemens Eisserer 2011-05-12 08:34:19 UTC
I still experience those crashes with fedora-14 with latest (~2011-05-01) updates from time to time, even when using the single-threaded collector.

Unfourtunatly when eclipse crashes, due to its own launcher, abrt is not notified about the crash, so the only other crash log I  have is netbeans crashing during startup.

It could also be a hardware fault, but I doubt it. My old laptop is rock-solid for non-java programs and passes memtest86 running for hours.

Comment 17 Clemens Eisserer 2011-05-17 09:02:50 UTC
happend just again - right after eclipse has started up and I maximized its main window - see hs_err_pid3412.log.

Comment 18 Clemens Eisserer 2011-05-17 09:03:16 UTC
Created attachment 499289 [details]
crash right after starting eclipse

Comment 19 Fedora End Of Life 2012-08-16 12:59:23 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping