unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kirill Ignatiev <kirill.ignatiev@gmail.com>,
	Dmitry Antipov <dmantipov@yandex.ru>
Cc: swiesner@lunaryorn.com, 19266@debbugs.gnu.org
Subject: bug#19266: 24.4; Font-related window redrawing delays on OS X
Date: Thu, 11 Dec 2014 19:45:35 +0200	[thread overview]
Message-ID: <8361dit70g.fsf@gnu.org> (raw)
In-Reply-To: <CACe-pWxphaJdwqnb8qXuqZJwDKH4nc2HP1Rv7t=Xyi41Vh2y4g@mail.gmail.com>

> Date: Wed, 10 Dec 2014 18:50:01 -0500
> From: Kirill Ignatiev <kirill.ignatiev@gmail.com>
> Cc: Sebastian Wiesner <swiesner@lunaryorn.com>, 19266@debbugs.gnu.org
> 
> Can someone familiar with emacs' font internals check if this makes
> sense as the cause of the problem, please? I really don't understand
> how/where fonts are stored/cached/used; I did read
> font/fontset/macfont/alloc.c, but I'm still unclear.

Unfortunately, we don't have too many experts on this, to put it
mildly.  Dmitry, could you please take a look?

> To summarize: My interpretation of what's happening is that when emacs
> looks at some fonts to see if they contain a certain characters and
> neither of them does, emacs *does not* cache the fonts. So the next
> time redisplay happens after those fonts are garbage-collected, emacs
> has to load the fonts all over again, causing a noticeable redisplay
> delay.

This does sound like the truth, although I'm not sure.

> For testing, how do I turn off font garbage collection, so that no
> font is ever closed?

Comment out the call to cleanup_vector?

> How do I trigger font garbage collection manually?

Did you try "M-x garbage-collect RET"?

> Is this the right mailing list for this?

Yes, it is.





  reply	other threads:[~2014-12-11 17:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  7:13 bug#19266: 24.4; Font-related window redrawing delays on OS X Kirill Ignatiev
2014-12-04  7:30 ` Eli Zaretskii
2014-12-04  7:41   ` Kirill Ignatiev
2014-12-04  8:03     ` Eli Zaretskii
2014-12-04  8:20       ` Kirill Ignatiev
2014-12-04  9:55   ` Sebastian Wiesner
2014-12-04 10:17     ` Eli Zaretskii
2014-12-04 10:19       ` Sebastian Wiesner
2014-12-07  5:50         ` Kirill Ignatiev
2014-12-07 16:09           ` Eli Zaretskii
2014-12-10 23:50             ` Kirill Ignatiev
2014-12-11 17:45               ` Eli Zaretskii [this message]
2014-12-12  2:10                 ` Kirill Ignatiev
2014-12-12  8:06                   ` Eli Zaretskii
2014-12-17  1:35                     ` Kirill Ignatiev
2014-12-17  2:13                       ` Kirill Ignatiev
2014-12-12  8:29                   ` Sebastian Wiesner
2014-12-12  9:33                     ` Kirill Ignatiev
2014-12-12 10:56                       ` Eli Zaretskii
2022-04-30 15:44 ` Lars Ingebrigtsen
2022-05-02 16:22   ` Kirill Ignatiev
2022-05-03  9:05     ` 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=8361dit70g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19266@debbugs.gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=kirill.ignatiev@gmail.com \
    --cc=swiesner@lunaryorn.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).