Bug 680992 - [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)
Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-50.1.8.7.fc13: Process /usr/lib/jvm/java-...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:180862e9d64767d28f653055ea3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-28 17:49 UTC by Paul M. Summitt
Modified: 2011-02-28 17:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-28 17:57:19 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (5.17 KB, text/plain)
2011-02-28 17:49 UTC, Paul M. Summitt 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Paul M. Summitt 2011-02-28 17:49:39 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: It just crashed 
component: java-1.6.0-openjdk
crash_function: pthread_cond_timedwait@@GLIBC_2.3.2
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
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: 1298788721
uid: 500

How to reproduce
-----
1. Had Vuse open
2.
3.
unknown
Comment 1 Paul M. Summitt 2011-02-28 17:49:42 UTC 
Created attachment 481421 [details]
File: backtrace
Comment 2 Deepak Bhole 2011-02-28 17:57:19 UTC 
Unfortunately the trace is insufficient to find probable cause. I am going to close this issue. But please re-open if it happens again/when you get a better trace.
Note You need to log in before you can comment on or make changes to this bug.