GNU bug report logs -
#6585
23.1; Hang / CPU 100% on background interaction when in minibuffer
Previous Next
Reported by: jcornez <at> ravenpack.com (Jason Cornez)
Date: Thu, 8 Jul 2010 16:24:02 UTC
Severity: normal
Found in version 23.1
Done: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> Date: Thu, 8 Jul 2010 16:19:06 +0200 (CEST)
> From: jcornez <at> ravenpack.com (Jason Cornez)
> Cc:
>
> However, if I am currently interacting with emacs in the minibuffer at
> the time the lisp tries to open the new window, then emacs hangs and
> consumes 100% CPU (for one core). By "iteracting" I simply mean that
> the emacs focus is in the minibuffer, such as for C-x C-f. I don't
> need to be actively typing or anything. That is, the minibuffer is
> active.
>
> The emacs process seems to be entirely unresponsive: the cursor stops
> blinking, no keyboard input is accepted, the menus do not activate,
> sending commands like "emacsclient -e '(abort-recursive-edit)'" just
> hang and do nothing. The only thing I can do is kill the emacs
> process.
You can help debugging this if you attach GDB to Emacs when it hangs
like that, and see where it is looping. The file etc/DEBUG in the
Emacs source tree has some advice how to debug these problems, under
"If the symptom of the bug is that Emacs fails to respond".
This bug report was last modified 13 years and 39 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.