Bug 668507 - [abrt] java-1.6.0-openjdk-1:1.6.0.0-46.1.8.3.fc13: os::abort: 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-46.1.8.3.fc13: os::abort: Process /usr/li...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 13
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:dd547b9475d08bfeb6bb1fbc42c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-10 16:56 UTC by Andrea Gazzaniga
Modified: 2011-03-28 16:47 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-28 16:47:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (170.23 KB, text/plain)
2011-01-10 16:56 UTC, Andrea Gazzaniga
no flags Details

Description Andrea Gazzaniga 2011-01-10 16:56:11 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/../../bin/java sun.applet.PluginMain /tmp/icedteaplugin-gazza/8791-icedteanp-plugin-to-appletviewer /tmp/icedteaplugin-gazza/8791-icedteanp-appletviewer-to-plugin
component: java-1.6.0-openjdk
crash_function: os::abort
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-46.1.8.3.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: 1294678292
uid: 500

How to reproduce
-----
1. joined a webex meeting
2. close the meeting
3. the crash has been reported.

Comment 1 Andrea Gazzaniga 2011-01-10 16:56:18 UTC
Created attachment 472646 [details]
File: backtrace

Comment 2 Deepak Bhole 2011-03-28 16:47:23 UTC
The error originated in JNI code from /home/gazza/.webex/1024/libtpwrap.so . There isn't anything the JVM can do about it. The bug should be opened with WebEx.


Note You need to log in before you can comment on or make changes to this bug.