Bug 137327 - emacs hangs when ispelling TeX files
emacs hangs when ispelling TeX files
Product: Fedora
Classification: Fedora
Component: aspell (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Ivana Varekova
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2004-10-27 11:45 EDT by David Monniaux
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-01 04:46:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Monniaux 2004-10-27 11:45:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3)

Description of problem:
When editing any .tex file, hitting M-$ (or any ispell function) hangs
the process (C-g can recover from it). M-x flyspell-mode hangs the
process in a way not recoverable from C-g.

The symptoms disappear if one disables the Ispell TeX parser:
(add-hook 'tex-mode-hook (function (lambda () (setq ispell-parser nil))))
(add-hook 'TeX-mode-hook (function (lambda () (setq ispell-parser nil))))
(add-hook 'LaTeX-mode-hook (function (lambda () (setq ispell-parser

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Open a .tex file
2.Hit M-$ on any word in the text (say, APPLICATION)

Actual Results:  Emacs shows "checking APPLICATION..." and hangs.

Expected Results:  It should tell me the word is correct and go on

Additional info:
Comment 1 Jens Petersen 2004-10-29 01:32:41 EDT
This sounds a bit like bug 54391, which I couldn't reproduce...

Do the same thing happen with "emacs -q --no-site-file" for you?
Comment 2 Jens Petersen 2004-10-29 01:35:10 EDT
Perhaps it is a aspell issue on x86_64?
Can you reproduce on a ix86 box? :)
Perhaps you'd like to try with say FC3test3
or the packages in rawhide now to see if it is any better.
Comment 3 David Monniaux 2004-10-29 02:33:51 EDT
The same problem happens with "emacs -q --no-site-file" on the AMD64

I do not have a non-AMD64 x86 box with Fedora Core 2 installed.

This is a workplace machine, it's not easy for me to go and install
experimental machines.
Comment 4 Brion Vibber 2004-10-29 03:01:04 EDT
I can confirm the hang on AMD64 and working on 32-bit Athlon.

$ touch empty.tex
$ emacs empty.tex
type "barf"
hit ESC
hit $

Result on single Athlon XP 2400+: it nicely confirms that the word "barf" is correctly 
Result on dual Opteron 248: prints 'Checking spelling of BARF...', then emacs hangs with 
100% CPU usage.

Both machines are running Fedora Core 2, package versions emacs-21.3-12, aspell
-0.50.3-19.1. Opteron is running 64-bit version. If I edit 'empty.txt' instead of 'empty.tex' 
the Opteron does not hang.
Comment 5 David Monniaux 2004-10-29 03:25:47 EDT
emacs loops on a read(3, "", 1024)=0 system call.

File descriptor 3 is a pipe (read end) to ispell, set to non-blocking
Comment 6 Jens Petersen 2004-11-01 03:25:45 EST
Ok, I see.  Does FC2 aspell work ok by itself on amd64?
Comment 7 David Monniaux 2004-11-01 09:48:35 EST
It looks like aspell works well standalone. At least, I can launch it
on the same file and it works ok.
Comment 8 David Monniaux 2004-11-03 13:00:04 EST
The problem does *not* appear on Debian pure64 with the following
emacs21   21.3+1-    The GNU Emacs editor
aspell    0.50.5-4                 GNU Aspell spell-checker
Comment 9 Jens Petersen 2004-11-03 21:28:17 EST
This seems to be an aspell issue as I suspected:

Downgrading to aspell-0.50.3-19.1 (fc2) on an fc3 install and
I can reproduce the problem.
Comment 10 Jens Petersen 2004-11-03 21:29:38 EST
(I forgot to add that it works in FC3.)
Comment 11 Ivana Varekova 2005-04-12 09:48:35 EDT
Can anybody reproduce this bug with the latest aspell package (aspell-0.50.5)?
Ivana Varekova
Comment 12 Ivana Varekova 2005-07-01 04:46:27 EDT
I'm closing this bug. If there is some problem please reopen it.

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