Bug 675982

Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-50.1.9.4.fc14: os::abort: 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: petr.brcak
Component: java-1.6.0-openjdkAssignee: Omair Majid <omajid>
Status: CLOSED DUPLICATE 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: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6631baf168db4e545e9429a76784941a0222b721
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 18:07:37 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

Description petr.brcak 2011-02-08 14:13:48 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: java -Xmx512m -Dsun.java2d.opengl=true -jar JDownloader.jar
component: java-1.6.0-openjdk
crash_function: os::abort
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java
kernel: 2.6.35.10-74.fc14.x86_64
package: java-1.6.0-openjdk-1:1.6.0.0-50.1.9.4.fc14
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 14 (Laughlin)
time: 1297174253
uid: 500

How to reproduce
-----
1.I use Jdownloader
2. App crash by use Jdownloader
3.
Comment 1 petr.brcak 2011-02-08 14:13:51 UTC 
Created attachment 477618 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 18:07:37 UTC 
Backtrace analysis found this bug to be similar to bug #657946, closing as duplicate.

Bugs which were found to be similar to this bug: bug #655942, bug #657946

This comment is automatically generated.

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