From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: npostavs@users.sourceforge.net, 28695@debbugs.gnu.org, bryan@bryan.sh
Subject: bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux
Date: Mon, 16 Oct 2017 05:30:49 +0300 [thread overview]
Message-ID: <8360bfhlie.fsf@gnu.org> (raw)
In-Reply-To: <a7913e45-8112-9d29-ee9e-45e90b174743@yandex.ru> (message from Dmitry Gutov on Mon, 16 Oct 2017 01:55:54 +0300)
> Cc: npostavs@users.sourceforge.net, bryan@bryan.sh, 28695@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 16 Oct 2017 01:55:54 +0300
>
> Children Self Comma Shared Object Symbol
> 0,03% 0,03% emacs libXext.so.6.4.0 [.] XdbeSwapBuffers
> 0,00% 0,00% emacs emacs [.] XdbeSwapBuffers@plt
Hmm... so do you see any difference between these 2 scenarios in other
parts of the profiles?
Thanks.
next prev parent reply other threads:[~2017-10-16 2:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 3:10 bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux Bryan Gilbert
2017-10-04 7:53 ` Eli Zaretskii
2017-10-04 9:04 ` martin rudalics
2017-10-04 9:32 ` Eli Zaretskii
2017-10-04 11:21 ` Bryan Gilbert
2017-10-04 11:36 ` Eli Zaretskii
2017-10-04 12:02 ` Bryan Gilbert
2017-10-04 12:31 ` Eli Zaretskii
2017-10-05 13:36 ` Dmitry Gutov
2017-10-05 14:01 ` Eli Zaretskii
2017-10-05 14:02 ` Noam Postavsky
2017-10-07 7:53 ` Dmitry Gutov
2017-10-07 8:14 ` Eli Zaretskii
2017-10-09 13:53 ` Dmitry Gutov
2017-10-09 14:03 ` Eli Zaretskii
2017-10-15 22:55 ` Dmitry Gutov
2017-10-16 2:30 ` Eli Zaretskii [this message]
2017-10-26 23:19 ` Dmitry Gutov
2017-10-28 9:33 ` Eli Zaretskii
2017-10-28 21:47 ` bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on GNU/Linux Richard Stallman
2017-10-05 14:26 ` bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux Bryan Gilbert
2022-04-23 13:46 ` Lars Ingebrigtsen
2022-05-22 11:28 ` Lars Ingebrigtsen
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=8360bfhlie.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28695@debbugs.gnu.org \
--cc=bryan@bryan.sh \
--cc=dgutov@yandex.ru \
--cc=npostavs@users.sourceforge.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).