From: Vincent Povirk <vincent@codeweavers.com>
Subject: Re: [=PATCH v5 2/2] gdiplus: In GdipPrivateAddMemoryFont allow loading fonts with long names
Message-Id: <CAAFPtVSYczrMP=V8xyetSgtK8=-cJd-fw9xfhXTQLirhuOdAfA@mail.gmail.com>
Date: Mon, 20 Nov 2017 11:36:01 -0600
In-Reply-To: <20171119194426.9003-2-dark.shadow4@web.de>
References: <20171119194426.9003-1-dark.shadow4@web.de> <20171119194426.9003-2-dark.shadow4@web.de>

> 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.