From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: contovob@tcd.ie, larsi@gnus.org, 42943@debbugs.gnu.org
Subject: bug#42943: 28.0.50; Emacsclient crashes in ftcrfont_glyph_extents
Date: Sat, 24 Oct 2020 18:52:48 +0300 [thread overview]
Message-ID: <83a6wbhb8v.fsf@gnu.org> (raw)
In-Reply-To: <m2k0vfk4wf.fsf@gmail.com> (message from Robert Pluim on Sat, 24 Oct 2020 17:41:36 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: contovob@tcd.ie, larsi@gnus.org, 42943@debbugs.gnu.org
> Date: Sat, 24 Oct 2020 17:41:36 +0200
>
> >> OK, so when we are about to release a font, we need to go over all the
> >> LGSTRING objects in gstring_hash_table, and remove from that cache
> >> every LGSTRING whose LGSTRING_FONT object holds the font we are about
> >> to release.
>
> Eli> Here, does the below give good results?
>
> I should really hit 'g' in Gnus before writing patches :-)
>
> That fixes it as well.
OK, thanks. (I think clearing the entire cache of gstrings is too
radical: we don't necessarily remove all the fonts from all the
frames.)
Now the important question: should we install this on master or on the
release branch? I believe the problem is not limited to 28.0.50, is
it? OTOH, is this safe enough to install on emacs-27?
next prev parent reply other threads:[~2020-10-24 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 0:47 bug#42943: 28.0.50; Emacsclient crashes in ftcrfont_glyph_extents Basil L. Contovounesios
2020-08-20 14:28 ` Eli Zaretskii
2020-08-21 14:05 ` Lars Ingebrigtsen
2020-10-22 12:41 ` Lars Ingebrigtsen
2020-10-22 22:11 ` Basil L. Contovounesios
2020-10-24 11:24 ` Robert Pluim
2020-10-24 11:46 ` Eli Zaretskii
2020-10-24 12:14 ` Robert Pluim
2020-10-24 13:10 ` Eli Zaretskii
2020-10-24 13:35 ` Robert Pluim
2020-10-24 13:27 ` Robert Pluim
2020-10-24 14:12 ` Eli Zaretskii
2020-10-24 14:48 ` Eli Zaretskii
2020-10-24 15:41 ` Robert Pluim
2020-10-24 15:52 ` Eli Zaretskii [this message]
2020-10-26 12:33 ` Robert Pluim
2020-10-26 16:16 ` Eli Zaretskii
2020-10-26 20:13 ` Basil L. Contovounesios
2020-10-24 15:34 ` Robert Pluim
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6wbhb8v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42943@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=rpluim@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.