Bug 669897

Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-46.1.8.3.fc13: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Will Humphreys <whumphreys>
Component: java-1.6.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: ahughes, dbhole, jvanek, langel, lkundrak, mjw, mmatejov, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:d6a0a15a3f0bfd66d37b2892f7e0fb369fc7feb5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-15 17:15:29 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 Will Humphreys 2011-01-15 16:37:06 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-will/5007-icedteanp-plugin-to-appletviewer /tmp/icedteaplugin-will/5007-icedteanp-appletviewer-to-plugin
comment: I have only played the game once and it crashed after about 10 minutes. I wasn't doing anything in particular. I think I had just missing shooting a droid.
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-46.1.8.3.fc13
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: 1295109030
uid: 500

How to reproduce
-----
1. Go to http://www.lasersquad.org/
2. Play the game for 10 minutes or so.
3. Crash.
Comment 1 Will Humphreys 2011-01-15 16:37:10 UTC 
Created attachment 473652 [details]
File: backtrace
Comment 2 Deepak Bhole 2011-01-15 17:15:29 UTC 
According to the trace, the VM ran out of memory. You will have to increase the amount of free memory available either by closing other applications, or by adding more RAM. 

You can check the amount of free memory available by running 'free -m' on a terminal (Applications -> System Tools -> Terminal). The first row shows total, used and free memory available.

If you still encounter the bug even after more free memory has been made available, please feel free to re-open this issue.