Bug 625208

Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13: raise: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Adam Goode <adam>
Component: java-1.6.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: dbhole, langel, lkundrak, mjw, mmatejov, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:045f7e0854b084c79a6bcb033daa1a129f2ea8cb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-19 16:00:17 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 Adam Goode 2010-08-18 21:10:15 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: java -Xmx512m -jar ij.jar
comment: Ran auto-updater in ImageJ.
component: java-1.6.0-openjdk
crash_function: raise
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java
kernel: 2.6.33.6-147.fc13.x86_64
package: java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13
rating: 3
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1282165559
uid: 9727
Comment 1 Adam Goode 2010-08-18 21:10:18 UTC 
Created an attachment (id=439512)
File: backtrace
Comment 2 Deepak Bhole 2010-08-19 15:28:09 UTC 
Is this error consistently reproducible?
Comment 3 Omair Majid 2010-08-19 16:00:17 UTC 

*** This bug has been marked as a duplicate of bug 560232 ***
Comment 4 Adam Goode 2010-08-19 16:01:20 UTC 
Only saw it once.
Comment 5 Adam Goode 2010-08-19 16:02:45 UTC 
Ah yes, the auto-updater in ImageJ replaces its running jar. So I guess this bug is known.