[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, 16 Aug 2016 05:38:34 +0300 |
> From: npostavs@users.sourceforge.net
> Cc: 24091@debbugs.gnu.org, acairncross@gmail.com, clement.pit@gmail.com
> Date: Sat, 13 Aug 2016 19:57:54 -0400
>
> >> > The question is: what happens if you bypass that loop and let Emacs
> >> > proceed with startup? Does it successfully finish the startup, or
> >> > does it error out or crash later on?
> >>
> >> Works fine, no crashes.
> >>
> >> >
> >> > If the former, we need to find a way to detect this special situation,
> >> > and maybe bypass the loop altogether.
> >>
> >> Hmm, not really sure where to start.
> >
> > I'd start by finding out why FRAME_ICONIFIED_P returns false.
>
> Well, it seems that's because Emacs never receives an UnmapNotify event.
> But that doesn't feel like I'm getting any closer to a solution...
What events does Emacs get in that case?