GNU bug report logs - #76121
31.0.50; crash in uniscribe_close

Previous Next

Full log

View this message in rfc822 format

From: Cecilio Pardo <cpardo <at> imayhem.com>
To: Pip Cet <pipcet <at> protonmail.com>
Cc: Richard Copley <rcopley <at> gmail.com>, 76121 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#76121: 31.0.50; crash in uniscribe_close
Date: Mon, 3 Mar 2025 18:41:58 +0100

[Message part 1 (text/plain, inline)]

On 01/03/2025 21:28, Pip Cet wrote:

> Just a heads-up: if uniscribe would benefit from a general mechanism to
> avoid calling the font_close method twice, it may well be worth doing
> it; the other font backends have been fixed to make font_close
> idempotent, but people are unlikely to stop writing font backends
> anytime soon :-)
> 
> Thanks for working on this!  If there's a uniscribe-specific fix that
> works, feel free to disregard this email.


The fix is simple, just setting dwrite_cache = NULL, as you already 
worked out.

From what I see, w32font_close is already idempotent, as it tests for a 
non-null hfont.

Thanks, and my apologies for not attending to this before.

[0001-Fix-bug-on-w32-uniscribe_close.patch (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.