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 #14 received at 22976 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andreas Schwab <schwab <at> suse.de>
Cc: 22976 <at> debbugs.gnu.org, eyal.lotem <at> gmail.com
Subject: Re: bug#22976: 24.5;
 setting unread-command-events to non cons puts emacs in 100% CPU use
Date: Thu, 10 Mar 2016 12:25:02 +0200

> From: Andreas Schwab <schwab <at> suse.de>
> Date: Thu, 10 Mar 2016 10:42:53 +0100
> Cc: 22976 <at> debbugs.gnu.org
> 
> Eyal Lotem <eyal.lotem <at> 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.

Previous Next

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