Bug 675852 - [abrt] java-1.6.0-openjdk-1:1.6.0.0-49.1.8.5.fc13: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 11 (SIGSEGV)
Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-49.1.8.5.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:c9c01726a43a5baafa54551fbe2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-07 22:47 UTC by Lee Lian Hoy
Modified: 2011-02-08 23:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-08 23:34:05 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (7.35 KB, text/plain)
2011-02-07 22:47 UTC, Lee Lian Hoy 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Lee Lian Hoy 2011-02-07 22:47:23 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-CrUZ/25234-icedteanp-plugin-to-appletviewer /tmp/icedteaplugin-CrUZ/25234-icedteanp-appletviewer-to-plugin
component: java-1.6.0-openjdk
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-49.1.8.5.fc13
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1297115921
uid: 500

How to reproduce
-----
1.Load Runescape
2.
3.
Comment 1 Lee Lian Hoy 2011-02-07 22:47:25 UTC 
Created attachment 477518 [details]
File: backtrace
Comment 2 Deepak Bhole 2011-02-08 15:11:02 UTC 
Sorry, it looks like the stack got corrupted and that left the trace incomplete, so I cannot tell what is wrong based on it. Can you reproduce this issue, or was it one time?
Comment 3 Lee Lian Hoy 2011-02-08 23:17:13 UTC 
So far, it is a one time thing. I've loaded it 3 times in total and it only happened on the 2nd attempt.
Comment 4 Deepak Bhole 2011-02-08 23:34:05 UTC 
Okay, I am going to close this for now. It is a bug, but there is nothing I can do with the available information unfortunately. Please feel free to re-open if it happens again.
Comment 5 Lee Lian Hoy 2011-02-08 23:40:01 UTC 
Will do, thanks!
Note You need to log in before you can comment on or make changes to this bug.