unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: david@ngdr.net
Cc: "25943@debbugs.gnu.org" <25943@debbugs.gnu.org>
Subject: bug#25943: 21.5  Frame Display Difficulties
Date: Sat, 08 Apr 2017 11:00:08 +0200	[thread overview]
Message-ID: <58E8A698.1060707@gmx.at> (raw)
In-Reply-To: <c83112151e64d00fb1f45d23806247d3@127.0.0.1>

 > The results are somewhat fascinating because of the differences in
 > performance, which, of course, you cannot see.  Sometimes problem 3 is
 > easy to see, sometimes it takes several frame creations and deletions.
 > There is one result where running over the network improves performance!
 > Running over the network is included because the results, and what I see,
 > make it hard to avoid speculating that timing/race conditions are at the
 > root of problem 3.

If

 > 25.1    Mneme   GTK3     Mneme    Yes
 > 25.1    Thalia  No       Thalia   Yes      Yes, but rare.
 > 26.0.50 Thalia  No       Thalia   Yes
 > 25.1    Erota   No       Erota    Yes

below mean that the network was not involved, then the results below
don't seem to confirm that speculation.

 > Here is some detail.  Computer Mneme and Erota run Linux Mint 18.1,
 > computer Thalia runs Trisquel 7.  I run emacs on all three, sometimes over
 > my small network.
 >
 > A "No" entry for problem 3 really means "Not Yet"; but I have tried many
 > times to generate the problem.
 >
 > Sometimes it is possible to see the separation of the emacs frame and the
 > WM window.  There can be a short period before the two coalesce
 > (flashing), or the two may stay separated.

Does "stay separated" mean that the separation continues forever even
after showing another buffer in the frame, splitting its root window,
demaximizing and again maximizing it?

 > Version Run     Toolkit  Display  Problem3
 > 25.1    Mneme   GTK3     Mneme    Yes
 >                 GTK3     Thalia   No       This is a surprising result,
 >                                            given the above; it can be
 >                                            viewed as a performance
 >                                            improvement.
 >                          Erota    Yes      Yes, but very rare.
 >
 > 25.1    Thalia  No       Thalia   Yes      Yes, but rare.
 >                          Mneme    Yes
 > 26.0.50 Thalia  No       Thalia   Yes
 >                          Mneme    Yes      This shows both short period
 >                                            and permanent frame separation.
 >
 > 25.1    Erota   No       Erota    Yes
 >                          Mneme    Yes
 > 26.0.50 Erota   GTK3     Erota    No
 >                          Mneme    No

The last two lines seem to indicate that running a GTK3 build of
26.0.50.0 on Erota gives the best results.  Did you try 26.0.50.0
GTK3 builds for your Thalia and Mneme machines?

martin





  reply	other threads:[~2017-04-08  9:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  3:51 bug#25943: 21.5 Frame Display Difficulties david
2017-03-03  8:13 ` martin rudalics
     [not found]   ` <af552a322a8a630796cbddf1133b6dbe@127.0.0.1>
2017-03-04  9:59     ` martin rudalics
2017-03-07  1:51       ` david
2017-03-07  9:45         ` martin rudalics
2017-03-08 22:58           ` david
2017-03-09  8:56             ` martin rudalics
2017-03-10 18:44               ` david
2017-03-11 10:21                 ` martin rudalics
2017-03-23  7:59                   ` martin rudalics
2017-03-28 22:43                     ` david
2017-03-29  7:36                       ` martin rudalics
2017-03-29 19:53                         ` david
2017-03-30  7:29                           ` martin rudalics
2017-04-01  4:35                             ` david
2017-04-01  7:36                               ` martin rudalics
     [not found]                                 ` <7ee8200b866d8067514fb8b0bb9e814b@127.0.0.1>
2017-04-02  7:55                                   ` martin rudalics
2017-04-04  0:35                                     ` david
2017-04-04  7:25                                       ` martin rudalics
2017-04-07  0:12                                         ` david
2017-04-07  5:56                                           ` martin rudalics
2017-04-07 21:16                                             ` david
2022-04-25 14:48                                               ` Lars Ingebrigtsen
2022-05-24 12:50                                                 ` Lars Ingebrigtsen
2017-04-07 21:19                                             ` david
2017-04-08  9:00                                               ` martin rudalics [this message]
2017-04-11  6:49                     ` martin rudalics

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58E8A698.1060707@gmx.at \
    --to=rudalics@gmx.at \
    --cc=25943@debbugs.gnu.org \
    --cc=david@ngdr.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).