From: Dominik Schrempf <dominik.schrempf@gmail.com>
To: npostavs@users.sourceforge.net
Cc: Ken Raeburn <raeburn@raeburn.org>,
acairncross@gmail.com, clement.pit@gmail.com,
24091@debbugs.gnu.org
Subject: bug#24091: 24.5; High CPU usage at startup while hidden
Date: Mon, 23 Jan 2017 18:14:07 +0100 [thread overview]
Message-ID: <87h94p8zs0.fsf@gmail.com> (raw)
In-Reply-To: <87ziilui68.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net's message of "Fri, 20 Jan 2017 23:54:23 -0500")
Works like a charm. So far, it didn't lead to any problems.
Thank you very much!
Dominik
On Fri, Jan 20 2017, npostavs@users.sourceforge.net wrote:
> merge 24091 17237
> tags 24091 fixed
> close 24091 26.1
> quit
>
> Ken Raeburn <raeburn@raeburn.org> writes:
>
>> On Jan 17, 2017, at 21:21, npostavs@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….
>
> Okay, pushed to master [1: 6a788d2], let's see if we're doing it right.
>
> PS Dominik I merged #17237 into this one since it appears to be the same
> problem which should be fixed by this patch, please report back if it's
> not.
>
> 1: 2017-01-20 23:36:26 -0500 6a788d2fc18c23dcfc5d0352649b2f690e9cbff7
> Don't wait for frame to become visible
next prev parent reply other threads:[~2017-01-23 17:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 23:11 bug#24091: 24.5; High CPU usage at startup while hidden aiken
2016-07-27 23:32 ` Noam Postavsky
2016-07-28 2:16 ` Clément Pit--Claudel
2016-07-28 17:43 ` aiken
2016-07-28 19:37 ` Clément Pit--Claudel
2016-07-28 20:21 ` aiken
2016-07-29 1:45 ` npostavs
2016-07-29 5:46 ` Eli Zaretskii
2016-07-30 13:54 ` Noam Postavsky
2016-07-30 15:41 ` Eli Zaretskii
2016-08-13 23:57 ` npostavs
2016-08-16 2:38 ` Eli Zaretskii
2016-09-03 17:29 ` Noam Postavsky
2016-09-03 17:45 ` Eli Zaretskii
2016-09-03 17:53 ` Noam Postavsky
2016-09-03 18:35 ` Eli Zaretskii
2016-09-03 18:40 ` Noam Postavsky
2016-09-03 18:51 ` Eli Zaretskii
2016-09-03 20:03 ` Noam Postavsky
2016-09-04 7:33 ` martin rudalics
2016-09-04 12:35 ` Noam Postavsky
2016-09-04 13:15 ` martin rudalics
2016-09-04 13:40 ` Noam Postavsky
2016-09-04 15:56 ` martin rudalics
2016-09-04 16:21 ` Noam Postavsky
2016-09-06 16:05 ` Eli Zaretskii
2017-01-13 10:19 ` Dominik Schrempf
2017-01-14 1:38 ` npostavs
2017-01-14 7:52 ` Eli Zaretskii
2017-01-16 23:36 ` Ken Raeburn
2017-01-17 3:40 ` Eli Zaretskii
2017-01-18 2:21 ` npostavs
2017-01-20 5:16 ` Ken Raeburn
2017-01-21 4:54 ` npostavs
2017-01-23 17:14 ` Dominik Schrempf [this message]
2017-10-26 17:22 ` bug#24091: Problem caused by the fix for this bug Ken Brown
2017-10-26 17:42 ` Noam Postavsky
2017-10-26 18:12 ` Ken Brown
2017-10-26 20:40 ` Noam Postavsky
2017-10-27 14:11 ` Ken Brown
2017-10-27 17:26 ` Eli Zaretskii
2017-10-27 17:53 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h94p8zs0.fsf@gmail.com \
--to=dominik.schrempf@gmail.com \
--cc=24091@debbugs.gnu.org \
--cc=acairncross@gmail.com \
--cc=clement.pit@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=raeburn@raeburn.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.