From: Markus Triska <markus.triska@gmx.at>
To: 84@emacsbugs.donarmstrong.com
Subject: bug#84: Acknowledgement (23.0.60; Occasional hangs in flyspell-mode and ispell-word)
Date: Tue, 08 Jul 2008 20:24:26 +0200 [thread overview]
Message-ID: <m11w24grol.fsf@gmx.at> (raw)
In-Reply-To: <m1fxqk33un.fsf@pnsgw1-client235.demo.tuwien.ac.at> (Markus Triska's message of "Tue, 08 Jul 2008 15:25:20 +0200")
> while flyspell-word waits for output; one can interrupt the wait with
> C-g
I've now seen that this wasn't the case in the backtrace, i.e., I
specifically could NOT interrupt accept-process-output; also, had I been
able to interrupt it, a subsequent process-send-string to the dead
process from flyspell-word would have triggered an error and thus
removed flyspell-post-command-hook from post-command-hook.
To sum up, I think it remains valid that accept-process-output should
throw an error (instead of waiting, as it currently does) if the process
it is waiting for is dead, and an independent issue is that
wait_reading_process_output can sometimes not be interrupted manually
and can make Emacs hang indefinitely. So far, the hangs seem to occur
when I have previously interrupted wait_reading_process_output when it
was waiting for output from a dead process. For example, I'm using the
following to enable flyspell mode when it was disabled:
(defun reactivate-flyspell ()
(unless (memq 'flyspell-post-command-hook post-command-hook)
(flyspell-mode 1)))
(setq my-idle (run-with-idle-timer 0.1 t 'reactivate-flyspell))
then I continuously kill aspell with:
$ while true; do killall -s 9 aspell; sleep 0.1; done
Then I go into a buffer with a lot of text and move the cursor over a
few words (to flyspell-them) until Emacs hangs due to
accept-process-output from a dead aspell process. I can always interrupt
this with C-g. I do this a few times, then stop the continuous killing
of aspell, and then start Gnus a few times. This almost always makes
Emacs hang completely; I'm now trying to make this test case shorter.
next prev parent reply other threads:[~2008-07-08 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080327052040.002826434E0@mt-computer.local>
[not found] ` <handler.84.B.120662569622724.ack@emacsbugs.donarmstrong.com>
2008-07-08 13:25 ` bug#84: Acknowledgement (23.0.60; Occasional hangs in flyspell-mode and ispell-word) Markus Triska
2008-07-08 18:24 ` Markus Triska [this message]
2008-07-09 9:57 ` Markus Triska
2008-07-10 23:01 ` Markus Triska
2008-07-12 15:56 ` Markus Triska
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m11w24grol.fsf@gmx.at \
--to=markus.triska@gmx.at \
--cc=84@emacsbugs.donarmstrong.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).