Bug 675852

Summary: [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)
Product: [Fedora] Fedora Reporter: Lee Lian Hoy <cruz>
Component: java-1.6.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: ahughes, dbhole, jvanek, langel, lkundrak, mjw, mmatejov, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:c9c01726a43a5baafa54551fbe246f8a6eb5a623
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-08 23:34:05 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 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!