From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Jim Radford <radford@blackbean.org>, 18501@debbugs.gnu.org
Subject: bug#18501: Acknowledgement (24.3.93; OS X; crash in free() when calling macfont_close())
Date: Mon, 22 Sep 2014 18:52:59 +0900 [thread overview]
Message-ID: <wlfvfknfr8.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <541CD37F.3030802@yandex.ru>
>>>>> On Sat, 20 Sep 2014 05:08:15 +0400, Dmitry Antipov <dmantipov@yandex.ru> said:
> On 09/19/2014 10:05 PM, Jim Radford wrote:
>> Here are the two calls that free the font:
>>
>> frame #1: 0x00000001001c5ffd Emacs`macfont_close(font=0x0000000105c2a8c0) + 13 at macfont.m:2621
>> frame #2: 0x000000010014de80 Emacs`font_clear_cache(f=<unavailable>, cache=<unavailable>, driver=<unavailable>) + 304 at font.c:2620
>>
>> frame #1: 0x00000001001c5ffd Emacs`macfont_close(font=0x0000000105c2a8c0) + 13 at macfont.m:2621
>> frame #2: 0x000000010011be9d Emacs`Fgarbage_collect [inlined] cleanup_vector + 38 at alloc.c:2935
>>
>> Notice that the pointer is the same in both cases. Both cleanup_vector() and font_clear_cache() call
>>
drv-> close(font)
>>
>> It seems that font_clear_cache is leaving the font around for the GC to clean up (a second time) later.
> Please try this.
Does this mean each font backend driver should prepare for multiple
"close" calls for a single font object? Or is this something specific
to OS X?
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2014-09-22 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 23:38 bug#18501: 24.3.93; OS X; crash in free() when calling macfont_close() Jim Radford
[not found] ` <handler.18501.B.141107709331502.ack@debbugs.gnu.org>
2014-09-18 22:14 ` bug#18501: Acknowledgement (24.3.93; OS X; crash in free() when calling macfont_close()) Jim Radford
2014-09-19 17:05 ` Jim Radford
2014-09-19 18:05 ` Jim Radford
2014-09-20 1:08 ` Dmitry Antipov
2014-09-20 22:08 ` Jim Radford
2014-09-21 5:03 ` Dmitry Antipov
2014-09-21 16:58 ` Jim Radford
2014-09-22 9:52 ` YAMAMOTO Mitsuharu [this message]
2014-09-22 11:01 ` Dmitry Antipov
2016-05-25 20:38 ` Alan Third
2016-05-27 9:29 ` Eli Zaretskii
2016-05-27 18:13 ` Alan Third
2016-05-27 18:56 ` Eli Zaretskii
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=wlfvfknfr8.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=18501@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=radford@blackbean.org \
/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).