unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Froemling <ericfroemling@gmail.com>
Cc: 17124@debbugs.gnu.org
Subject: bug#17124: 24.3.50; Occasional Extremely Slow Redraws in OSX Emacs
Date: Tue, 01 Apr 2014 18:03:18 +0300	[thread overview]
Message-ID: <83d2h1ccsp.fsf@gnu.org> (raw)
In-Reply-To: <C9B50E0E-A523-47DF-8DB2-BBDD6079991D@gmail.com>

> From: Eric Froemling <ericfroemling@gmail.com>
> Date: Mon, 31 Mar 2014 22:23:33 -0700
> Cc: 17124@debbugs.gnu.org
> 
> Ok here’s some further info/possible repro case if it is of use:
> I built my own emacs by doing a bzr branch bzr://bzr.sv.gnu.org/emacs/trunk,
> then autogen.sh and ./configure —with-ns
> I removed my .emacs file so as to get default settings, then launched emacs,
> opened a large text file, and subdivided the frame into several windows.
> With this setup it is quite easy for me to get the slowdown to happen by just
> dragging a divider around for a bit.
> Here’s a clip of a slowdown with the activity monitor visible:
> https://www.youtube.com/watch?v=olkyqVOWSLs
> You can see that emacs is only using a few percent cpu throughout the slow redraw,
> whatever that may imply.

If Emacs does not use too much CPU cycles, it's probably not an Emacs
problem.

> I’ve also attached a sample I took of emacs during such a slowdown.
> It looks like a lot of calls are blocking in _CGSSynchronizeWindowBackingStore
> under the hood.

I don't know how to read that.  Are the numbers there CPU times, or
are they numbers of calls to each function?  If the latter, then they
are not very useful in this case.

Thanks.





  reply	other threads:[~2014-04-01 15:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 21:23 bug#17124: 24.3.50; Occasional Extremely Slow Redraws in OSX Emacs Eric Froemling
2014-03-28  7:20 ` Eli Zaretskii
2014-03-28 16:19   ` Eric Froemling
2014-03-28 17:43     ` Eli Zaretskii
2014-04-01  5:23       ` Eric Froemling
2014-04-01 15:03         ` Eli Zaretskii [this message]
2014-04-01 16:57           ` Eric Froemling
2014-06-27 10:44             ` Jan Djärv
2014-06-27 13:37               ` Eli Zaretskii
2014-06-27 17:13                 ` Jan Djärv
2014-06-27 17:30                   ` Eric Froemling
2014-06-27 19:58                     ` Eli Zaretskii
2014-06-27 19:57                   ` Eli Zaretskii
2014-06-30 12:55                     ` Jan Djärv
2014-06-30 14:45                       ` Eli Zaretskii
2014-03-29 12:20 ` Jan Djärv
2015-01-27 20:09 ` Bill Sacks
2016-02-10 19:25   ` bulldozer
2016-02-10 23:29     ` Alan Third
2016-02-11  0:26       ` bulldozer
2016-02-12  5:10       ` bulldozer
2016-02-12  7:21         ` Eli Zaretskii
2016-02-12 23:54           ` Alan Third
2020-09-09 12:30             ` bug#16594: " 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=83d2h1ccsp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17124@debbugs.gnu.org \
    --cc=ericfroemling@gmail.com \
    /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).