GNU bug report logs - #22976
24.5; setting unread-command-events to non cons puts emacs in 100% CPU use

Previous Next

Full log

Message #28 received at 22976-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Eyal Lotem <eyal.lotem <at> gmail.com>
Cc: schwab <at> suse.de, 22976-done <at> debbugs.gnu.org
Subject: Re: bug#22976: 24.5; setting unread-command-events to non cons puts
 emacs in 100% CPU use
Date: Sat, 26 Mar 2016 11:54:32 +0300

> Date: Thu, 10 Mar 2016 14:40:24 +0200
> From: Eyal Lotem <eyal.lotem <at> gmail.com>
> Cc: Andreas Schwab <schwab <at> suse.de>, 22976 <at> debbugs.gnu.org
> 
>  > 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".
> 
>  Exactly. So these values aren't ignored, they create an illusion that
>  some input is available. I was thinking about ignoring them entirely,
>  i.e. treating such values as nil (and maybe even silently replacing
>  them with nil).
> 
> Ah, sorry I misunderstood originally!
> 
> That sounds good to me (though it would be slightly better to warn about it somewhere, IMO)

No further comments, so I installed a fix along the above-mentioned
lines on the emacs-25 branch, and I'm marking this bug done.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.