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

Previous Next

Full log

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

From: npostavs <at> users.sourceforge.net
To: Dominik Schrempf <dominik.schrempf <at> gmail.com>
Cc: 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, 13 Jan 2017 20:38:02 -0500

[Message part 1 (text/plain, inline)]

tags 24091 patch
quit

Dominik Schrempf <dominik.schrempf <at> gmail.com> writes:

> I do not want to bring up old threads,

On the contrary, please do feel free to bring up any open bug thread.

> but I am having the exact same problem with Emacs+XMonad for years
> now.

That's interesting information, because I thought that loop was supposed
to be working for XMonad.

> Did you come to a conclusion or find a fix back in September?

We left things inconclusive, but revisiting this now, I see no reason
against simply removing this waiting loop:

[v1-0001-Don-t-wait-for-frame-to-become-visible.patch (text/plain, attachment)]

[Message part 3 (text/plain, inline)]

> On Tue, Sep 06 2016, Eli Zaretskii wrote:
>>
>> Maybe we should stop waiting after some time has passed, like 0.5
>> sec.  Does that work in this case?  Does the frame always appears
>> within half a second when workspaces are not involved?

I don't think any particular timed wait can be guaranteed to work in all
cases, since this involves multiple processes.

Previous Next

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