From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 20890@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#20890: master 1233bcb: Work around GC+Cairo bug
Date: Wed, 04 Apr 2018 16:44:04 +0300 [thread overview]
Message-ID: <831sfv3x3v.fsf@gnu.org> (raw)
In-Reply-To: <87lge3w4t7.fsf@gmail.com> (message from Robert Pluim on Wed, 04 Apr 2018 14:10:12 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 20890@debbugs.gnu.org, eggert@cs.ucla.edu
> Date: Wed, 04 Apr 2018 14:10:12 +0200
>
> > If you can tell why FT_List_Find crashes, in terms of Emacs variables
> > and data structures, maybe we can figure out what is going on here.
> > But in any case, I think we should put the same workaround in
> > ftcrfont_close as we did in ftfont_close, because the former calls the
> > latter, and we then risk the situation where we only half-close the
> > font when ftcrfont_close is called from GC.
>
> That same workaround fixes it on Ubuntu.
Then I think we should install it.
next prev parent reply other threads:[~2018-04-04 13:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180403152442.25413.61540@vcs0.savannah.gnu.org>
[not found] ` <20180403152443.B15F6215A9@vcs0.savannah.gnu.org>
2018-04-03 22:14 ` master 1233bcb: Work around GC+Cairo bug Robert Pluim
2018-04-04 6:31 ` Eli Zaretskii
2015-06-24 10:26 ` bug#20890: 25.0.50; build from git crashes on startup Robert Marshall
2015-07-26 20:30 ` Paul Eggert
2018-04-03 9:39 ` Robert Pluim
2018-04-03 10:06 ` Eli Zaretskii
2018-04-03 15:03 ` Paul Eggert
2018-04-03 15:13 ` Eli Zaretskii
2018-04-03 15:26 ` Paul Eggert
2018-04-04 8:52 ` bug#20890: master 1233bcb: Work around GC+Cairo bug Robert Pluim
2018-04-04 9:08 ` Eli Zaretskii
2018-04-04 12:10 ` Robert Pluim
2018-04-04 13:44 ` Eli Zaretskii [this message]
2018-04-04 18:00 ` Paul Eggert
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=831sfv3x3v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20890@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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.