From: Eyal Lotem <eyal.lotem@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>, 22976@debbugs.gnu.org
Subject: bug#22976: 24.5; setting unread-command-events to non cons puts emacs in 100% CPU use
Date: Thu, 10 Mar 2016 12:34:08 +0200 [thread overview]
Message-ID: <CALA94fOzDcKqV7LU=ujV4495CpYzDr1G6jDgqO22qf61Ekm_4Q@mail.gmail.com> (raw)
In-Reply-To: <838u1qmxz5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
It can be set to any value at all, unfortunately.
The problem now is that non-cons/non-nil values are ignored.
The loop to repeatedly thinks there's input so it consumes 100% cpu, each
iteration seeing that it isn't a cons cell, so there's "nothing to do".
On Thu, Mar 10, 2016 at 12:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Andreas Schwab <schwab@suse.de>
> > Date: Thu, 10 Mar 2016 10:42:53 +0100
> > Cc: 22976@debbugs.gnu.org
> >
> > Eyal Lotem <eyal.lotem@gmail.com> writes:
> >
> > > As can be reproduced easily:
> > >
> > > (setq unread-command-events 1) -- emacs now at 100% CPU
> > > (setq unread-command-events nil) -- emacs OK again
> >
> > Don't do that then.
>
> Can unread-command-events be anything but nil or a cons cell? If not,
> we could change the few tests of the value to explicitly ignore
> non-nil, non-cons values. Do you see any immediate problems with such
> a change?
>
> Thanks.
>
--
Eyal
[-- Attachment #2: Type: text/html, Size: 1639 bytes --]
next prev parent reply other threads:[~2016-03-10 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 8:37 bug#22976: 24.5; setting unread-command-events to non cons puts emacs in 100% CPU use Eyal Lotem
2016-03-10 9:42 ` Andreas Schwab
2016-03-10 9:47 ` Eyal Lotem
2016-03-10 10:25 ` Eli Zaretskii
2016-03-10 10:34 ` Eyal Lotem [this message]
2016-03-10 10:39 ` Eli Zaretskii
2016-03-10 12:40 ` Eyal Lotem
2016-03-26 8:54 ` Eli Zaretskii
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='CALA94fOzDcKqV7LU=ujV4495CpYzDr1G6jDgqO22qf61Ekm_4Q@mail.gmail.com' \
--to=eyal.lotem@gmail.com \
--cc=22976@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@suse.de \
/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).