From: Eli Zaretskii <eliz@gnu.org>
To: Darren Hoo <darren.hoo@gmail.com>
Cc: eggert@cs.ucla.edu, 16594@debbugs.gnu.org
Subject: bug#16594: 24.3.50; very slow redraw when resizing windows horizontally
Date: Sun, 02 Feb 2014 17:57:53 +0200 [thread overview]
Message-ID: <83ha8h4ida.fsf@gnu.org> (raw)
In-Reply-To: <m2mwia5bhl.fsf@gmail.com>
> From: Darren Hoo <darren.hoo@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 16594@debbugs.gnu.org
> Date: Sun, 02 Feb 2014 13:28:54 +0800
>
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
> >
> > Continuing on my guess, which may well be a wild goose chase, can you
> > use DTrace to see what system calls the offending Emacs is executing?
>
> I earlier used Xcode's instrument which I believe just interprets the
> output from Dtrace/Dtruss. This argb32_image_mark_rgb32 low level call
> is the top one which is in turn called by x_write_glyphs up on the call
> tree. But as Eli has pointed out and I quote:
>
> Given that dragging the divider involves redrawing every line in
> every window, these times are entirely reasonable.
I was talking only about the times spent inside redisplay_internal,
update_window, and update_window_line. The overall redrawing
behavior, as seen in the screencast, does not seem reasonable to me.
next prev parent reply other threads:[~2014-02-02 15:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 8:01 bug#16594: 24.3.50; very slow redraw when resizing windows horizontally Darren Hoo
2014-01-30 13:47 ` martin rudalics
2014-01-30 15:39 ` Darren Hoo
2014-01-30 16:14 ` Eli Zaretskii
2014-01-30 15:44 ` Stefan Monnier
2014-01-30 16:27 ` Eli Zaretskii
2014-01-30 16:53 ` martin rudalics
2014-01-30 17:27 ` martin rudalics
2014-01-30 17:33 ` Eli Zaretskii
2014-01-30 17:57 ` martin rudalics
2014-01-30 17:58 ` Eli Zaretskii
2014-01-30 18:57 ` Darren Hoo
2014-01-30 20:17 ` Eli Zaretskii
2014-01-31 3:16 ` Darren Hoo
2014-01-31 8:22 ` Eli Zaretskii
2014-01-31 9:58 ` Jan D.
2014-01-31 11:31 ` Eli Zaretskii
2014-01-31 12:13 ` Jan D.
2014-01-31 12:54 ` Darren Hoo
2014-01-31 13:47 ` Jan D.
2014-01-31 13:57 ` Darren Hoo
2014-01-30 18:46 ` martin rudalics
2014-01-30 21:57 ` Stefan Monnier
2014-01-31 10:42 ` martin rudalics
2014-01-30 16:39 ` Darren Hoo
2014-01-30 16:15 ` Eli Zaretskii
2014-01-31 20:56 ` Darren Hoo
2014-02-01 6:08 ` Paul Eggert
2014-02-01 9:12 ` Darren Hoo
2014-02-01 17:46 ` Eli Zaretskii
2014-02-02 0:52 ` Paul Eggert
2014-02-02 5:28 ` Darren Hoo
2014-02-02 15:57 ` Eli Zaretskii [this message]
2014-02-02 20:48 ` Paul Eggert
2014-02-03 19:27 ` Paul Eggert
2014-02-06 13:06 ` Darren Hoo
2014-02-06 15:23 ` Darren Hoo
2014-02-06 18:34 ` Paul Eggert
2014-02-06 22:14 ` Stefan Monnier
2014-02-08 22:43 ` Darren Hoo
2014-02-09 4:17 ` Paul Eggert
2014-02-09 6:42 ` Darren Hoo
2014-02-09 7:09 ` Adrian Robert
2014-02-09 7:16 ` Adrian Robert
2014-02-09 19:43 ` Stefan Monnier
2014-02-11 6:03 ` Jan Djärv
2014-03-09 13:27 ` Jan Djärv
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=83ha8h4ida.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16594@debbugs.gnu.org \
--cc=darren.hoo@gmail.com \
--cc=eggert@cs.ucla.edu \
/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).