Bug 669897 - [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)
Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-46.1.8.3.fc13: Process /usr/lib/jvm/java-...
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:d6a0a15a3f0bfd66d37b2892f7e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-15 16:37 UTC by Will Humphreys
Modified: 2011-01-15 17:15 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-15 17:15:29 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (35.44 KB, text/plain)
2011-01-15 16:37 UTC, Will Humphreys
no flags Details

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.


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