Bug 669631

Summary: [abrt] emacs-1:23.2-7.fc14: hash_lookup: Process /usr/bin/emacs-23.2 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Fran Taylor <narf>
Component: emacsAssignee: Karel Klíč <kklic>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: jonathan.underwood, kklic, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6e2157c6e3f3e1fd027162d8019de8dad6cad91b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-18 17:37:02 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 Fran Taylor 2011-01-14 07:02:48 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: emacs
component: emacs
crash_function: hash_lookup
executable: /usr/bin/emacs-23.2
kernel: 2.6.35.10-74.fc14.x86_64
package: emacs-1:23.2-7.fc14
rating: 3
reason: Process /usr/bin/emacs-23.2 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1294987759
uid: 500

comment
-----
emacs ran better on Multics and TOPS-20 than it does on Fedora.

This is not the only bad emacs bug.  In practice it's barely usable with its weird behavior.  What is going on?  I have never before seen a "released" platform where emacs runs so poorly.  

How to reproduce
-----
1. this is a vmware fusion vm, the files are on a gvfs partition
2. edit java source files for hours
3. run M-x compile to build java programs, and esc-` to parse error messages
4. try running java programs in gnome-terminal shell window, to see if they work
5. edit more source code
6. lather rinse repeat until... 
7. boom! random crash out of nowhere
Comment 1 Fran Taylor 2011-01-14 07:02:50 UTC 
Created attachment 473477 [details]
File: backtrace
Comment 2 Karel Klíč 2011-04-18 17:37:02 UTC 

*** This bug has been marked as a duplicate of bug 667884 ***