|
| From: | Jason S. Cornez |
| Subject: | bug#6585: 23.1; Hang / CPU 100% on background interaction when in minibuffer |
| Date: | Thu, 15 Jul 2010 17:59:33 +0200 |
| User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12pre) Gecko/20100712 Lightning/1.0b1 Shredder/3.0.7pre ThunderBrowse/3.3.1 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/15/2010 05:53 PM, Johan Bockgård wrote: > Note that quitting is inhibited for code that runs from timers or > process filters etc. (I don't know if this is your problem.) I've fully explained the situation above. The message which does initiate the elisp function with the infinite loop does come from an external process. So while there is obviously a bug in the elisp code (which I've now fixed) the resulting non-responsive emacs consuming the CPU seems like a bad thing and I really think I ought to be able to quit from this situation - indeed that I ought to be able to quit from just about any situation. - -Jason -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkw/MGUACgkQQlm6HDTMLyPNXQCg6B/4WdyNIOxu/axl5mg4m6jv eFoAoPVsDn0RQ1ncsQuSCm+oYxE/AkWP =+AsD -----END PGP SIGNATURE-----
| [Prev in Thread] | Current Thread | [Next in Thread] |