GNU bug report logs - #24091
24.5; High CPU usage at startup while hidden

Previous Next

Package: emacs;

Reported by: aiken <acairncross <at> gmail.com>

Date: Wed, 27 Jul 2016 23:25:01 UTC

Severity: normal

Tags: confirmed, fixed, patch

Merged with 20335

Found in versions 24.4, 24.5, 25.1-rc1

Fixed in version 26.1

Done: npostavs <at> users.sourceforge.net

Bug is archived. No further changes may be made.

Full log

Message #107 received at 24091 <at> debbugs.gnu.org (full text, mbox):

From: Ken Raeburn <raeburn <at> raeburn.org>
To: npostavs <at> users.sourceforge.net
Cc: dominik.schrempf <at> gmail.com, Eli Zaretskii <eliz <at> gnu.org>,
 acairncross <at> gmail.com, clement.pit <at> gmail.com, 24091 <at> debbugs.gnu.org
Subject: Re: bug#24091: 24.5; High CPU usage at startup while hidden
Date: Fri, 20 Jan 2017 00:16:24 -0500

On Jan 17, 2017, at 21:21, npostavs <at> users.sourceforge.net wrote:
> 
> Do we know about any operations that require the frame be visible?  What
> happens when they're run with an invisible frame?  Error?  Corrupted
> display?  Hang?

If drawing is done to an unmapped window, the X server can discard the data, but once the window is made visible, we should get an Expose event which would cause us to repaint the window.  The size and position of the window could be set by the window manager, and dropping the loop may mean we get to run a little more code than we used to before we get notified of the changes.  But these are things we have to deal with anyway, not just at window creation.  If we’re doing it right, AFAIK, we should be okay….

Ken
This bug report was last modified 7 years and 264 days ago.

Previous Next

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