[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#24091: 24.5; High CPU usage at startup while hidden

From: Eli Zaretskii
Subject: bug#24091: 24.5; High CPU usage at startup while hidden
Date: Tue, 17 Jan 2017 05:40:02 +0200

> From: Ken Raeburn <address@hidden>
> Date: Mon, 16 Jan 2017 18:36:05 -0500
> Cc: address@hidden,
>  address@hidden,
>  address@hidden,
>  address@hidden,
>  address@hidden
> > But maybe I'm wrong.  Ken, can you comment on this, please?
> As I understand it, from the function’s comments and stuff I’ve read so far 
> about the X11 and window manager protocols, the function already cannot 
> guarantee that the window is visible when it returns, it can only request of 
> the window manager that it make the window visible, which may or may not 
> happen soon.  In that sense, I think Noam’s right and we could just discard 
> the loop.
> On the other hand, there are probably environments and situations (depending 
> on the use of virtual desktops, choice of window manager, etc) where the 
> current code does, in fact, wait for the window to appear, and won’t any more 
> if we remove the loop.  Given that we should redraw things on expose events 
> anyway, I’m not sure it'll matter, unless someone’s following up a call to 
> make-frame-visible with some other action that needs to be delayed until 
> after the window is actually visible.  I think it’s probably worth trying it 
> to see if any differences are noticed under any of the environments people 
> are using.

OK, let's try.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]