Subject: bug#76121: 31.0.50; crash in uniscribe_close

From: Richard Copley <[email-masked]>
Date: Fri, 7 Feb 2025 16:24:36 +0000

Pip Cet wrote:

> My guess is if we made uniscribe_close return immediately if
> uniscribe_font->cache is NULL, this crash might be avoided.

That does seem to work. Thanks.
Another way to ensure idempotence is to set
'uniscribe_font->dwrite_cache' to NULL after calling
'w32_dwrite_free_cached_face'. This also seems to avoid the crash.