Bug 680152

Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-50.1.8.7.fc13: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Paul M. Summitt <psummitt>
Component: eclipseAssignee: Alexander Kurtakov <akurtako>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: ahughes, akurtako, dbhole, ebaron, jvanek, langel, lkundrak, mjw, mmatejov, oliver, omajid, overholt, sgehwolf, zx
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:d151a4c43259f0c7415f71070863c75afdcb8b06
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 12:09:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Paul M. Summitt 2011-02-24 14:00:00 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: java -Dazureus.install.path=/home/paul/.azureus/app -Dazureus.script.version=2 -Dazureus.script=/usr/bin/azureus org.gudy.azureus2.ui.swt.Main
comment: Unknown cause for crash
component: java-1.6.0-openjdk
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java
kernel: 2.6.34.7-66.fc13.i686
package: java-1.6.0-openjdk-1:1.6.0.0-50.1.8.7.fc13
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1298225617
uid: 500

How to reproduce
-----
1.  Normal use
2.
3.

Comment 1 Paul M. Summitt 2011-02-24 14:00:03 UTC
Created attachment 480760 [details]
File: backtrace

Comment 2 Deepak Bhole 2011-02-24 14:13:16 UTC
The error started in JNI code at Java_org_eclipse_swt_internal_gtk_OS__1gdk_1flush(). Reassigning to Eclipse.

Comment 3 Alexander Kurtakov 2011-03-30 10:49:35 UTC
Is this reproducible?
Is azureus installed from Fedora repositories?
Any other info that may help us?

Comment 4 Paul M. Summitt 2011-03-31 17:09:09 UTC
Yes it is reproducible.  I still have no idea what causes it.
Yes, azureus was/is installed from Fedora repositories.
I can send another backtrace next time it happens.  Don't know what else I can do.

Comment 5 Bug Zapper 2011-05-30 11:14:27 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 6 Bug Zapper 2011-06-27 12:09:18 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.