From: karthik nayak <karthik.188@gmail.com>
Date: Mon, 12 Aug 2024 08:43:22 GMT
Subject: Re: [PATCH v2 03/22] object-file: fix memory leak when reading corrupted headers
Message-ID: <CAOLa=ZRFYL6mWABumWM9pra+749tz7kOg3y9x5Pj9EdQxjC6eA@mail.gmail.com>
In-Reply-To: <43a38a2281f25db837dc9b5a59ecbe12214ac7bf.1723121979.git.ps@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> When reading corrupt object headers in `read_loose_object()`, then we

s/then//

> bail out immediately. This causes a memory leak though because we would
> have already initialized the zstream in `unpack_loose_header()`, and it
> is the callers responsibility to finish the zstream even on error. While
> this feels weird, other callsites do it correctly already.
>
> Fix this leak by ending the zstream even on errors. We may want to
> revisit this interface in the future such that the callee handles this
> for us already when there was an error.
>

[snip]