unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kirill Ignatiev <kirill.ignatiev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
	Sebastian Wiesner <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 21:10:32 -0500	[thread overview]
Message-ID: <CACe-pWykeS7AMdetb1j7dvoMbpi56-Cibw6NJdCkmkU3s2G4CA@mail.gmail.com> (raw)
In-Reply-To: <8361dit70g.fsf@gnu.org>

On 11 December 2014 at 12:45, Eli Zaretskii <eliz@gnu.org> wrote:
>> 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
>
> Comment out the call to cleanup_vector?

Oops, I only tried to turn compact_font_cache_entry into a noop. But
neither that, nor doing nothing in cleanup_vector works. If I comment
out drv->close, I see a bunch of calls to drv->close not being made,
but new fonts are *still* being opened in font_open_entity.

I'm guessing that when fonts are garbage collected, they are already
genuinely discarded, not pointed to from elisp structures (or where
they are stored), and are genuine garbage. Do you know where the
pointers to fonts live? I haven't figured out where they are being
discarded, and I'd like to stop them from becoming garbage in the
first place.

>
>> How do I trigger font garbage collection manually?
>
> Did you try "M-x garbage-collect RET"?

Yes, but it doesn't seem to trigger closing fonts. Perhaps there is
some other process at work there?

Thanks for your help, these redrawing delays are really irritating.





  reply	other threads:[~2014-12-12  2:10 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
2014-12-12  2:10                 ` Kirill Ignatiev [this message]
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=CACe-pWykeS7AMdetb1j7dvoMbpi56-Cibw6NJdCkmkU3s2G4CA@mail.gmail.com \
    --to=kirill.ignatiev@gmail.com \
    --cc=19266@debbugs.gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=eliz@gnu.org \
    --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).