Bug 672808

Summary: [abrt] xscreensaver-gl-extras-1:5.12-9.fc14: Process /usr/libexec/xscreensaver/molecule was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Odysseus <ericquerelle>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ajax, mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:77fe871c4ff7b56a61918dbce3c99cb3a585ab08
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-03 19:25:45 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 Odysseus 2011-01-26 13:31:19 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: molecule -root
component: xscreensaver
executable: /usr/libexec/xscreensaver/molecule
kernel: 2.6.35.10-74.fc14.i686
package: xscreensaver-gl-extras-1:5.12-9.fc14
rating: 3
reason: Process /usr/libexec/xscreensaver/molecule was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296047923
uid: 500

How to reproduce
-----
1.did nothing special
2.screensaver pobably crashed because of a lack of ram's
3.
Comment 1 Odysseus 2011-01-26 13:31:22 UTC 
Created attachment 475387 [details]
File: backtrace
Comment 2 Mamoru TASAKA 2011-01-26 14:08:27 UTC 
Once switching to mesa. I don't know if this is related to ram.
Comment 3 Adam Jackson 2012-01-03 19:25:45 UTC 
Mass close of abrt reports against F14.  Please update to at least F15, and reopen if this issue still occurs for you.