Bug 641416

Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-42.b18.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: Norberto <manuelinade>
Component: java-1.6.0-openjdkAssignee: Denis Lila <dlila>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: ahughes, dbhole, jvanek, langel, lkundrak, mjw, mmatejov, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:cbe683451e4688bd0744c9c62701279607de96ad
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-28 20:58:15 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 Norberto 2010-10-08 16:08:41 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: java -Dazureus.install.path=/home/norberto/.azureus/app -Dazureus.script.version=2 -Dazureus.script=/usr/bin/azureus org.gudy.azureus2.ui.swt.Main
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-56.fc13.i686
package: java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13
rating: 4
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: 1286488309
uid: 500
Comment 1 Norberto 2010-10-08 16:08:45 UTC 
Created attachment 452375 [details]
File: backtrace
Comment 2 Omair Majid 2010-10-08 16:15:04 UTC 
Is this error reproducible? Did it start happening recently? Can you please describe how to make this crash happen? This looks like a real bug in the JDK but unless I can reproduce it locally, I wont be able to fix it.
Comment 3 Denis Lila 2011-03-28 20:58:15 UTC 

*** This bug has been marked as a duplicate of bug 688453 ***