Bug 647258

Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-43.1.8.2.fc13: raise: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/javaws was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Arnold Sutter <noldi>
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: ahughes, dbhole, jvanek, langel, lkundrak, mjw, mmatejov, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:4bc246edb958df5a31ac1b5d08c649b61321a0b8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-27 19:01:31 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 Arnold Sutter 2010-10-27 17:41:26 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/javaws -J-Xmx512m -Xnofork /home/noldi/.netx/cache/http/www.sweethome3d.com/SweetHome3D.jnlp
comment: I started the "Sweet Home 3D" Icon on my desktop. It started, but this trace has been produced nevertheless. 
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/javaws
kernel: 2.6.34.7-61.fc13.x86_64
package: java-1.6.0-openjdk-1:1.6.0.0-43.1.8.2.fc13
rating: 3
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/javaws was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1288200666
uid: 500

How to reproduce
-----
1. Running the javaws application "Sweet Home 3D"
2. 
3.
Comment 1 Arnold Sutter 2010-10-27 17:41:29 UTC 
Created attachment 456037 [details]
File: backtrace
Comment 2 Deepak Bhole 2010-10-27 19:01:31 UTC 

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