From: Nikolay Sivov <bunglehead@gmail.com>
Subject: Re: [=PATCH v5 2/2] gdiplus: In GdipPrivateAddMemoryFont allow loading fonts with long names
Message-Id: <17cea83c-384c-e51d-da8f-8605c6fa1e31@gmail.com>
Date: Mon, 20 Nov 2017 20:38:14 +0300
In-Reply-To: <CAAFPtVSYczrMP=V8xyetSgtK8=-cJd-fw9xfhXTQLirhuOdAfA@mail.gmail.com>
References: <20171119194426.9003-1-dark.shadow4@web.de> <20171119194426.9003-2-dark.shadow4@web.de> <CAAFPtVSYczrMP=V8xyetSgtK8=-cJd-fw9xfhXTQLirhuOdAfA@mail.gmail.com>

On 20.11.2017 20:36, Vincent Povirk wrote:
>> v5
>> Don't cleanup family, since GdipDeletePrivateFontCollection already seems to do that
> 
> It'd be nice to follow up on this. Currently, our
> GdipGetFontCollectionFamilyList clones all the families, which would
> be leaking them. We can't check whether they're being freed, but we
> can check whether calling the function multiple times gives us the
> same pointer.
> 
> 

I actually have a patch for that, for system collection it returns new
pointer second time you call it.