Small memory leak when calling cgif_close() without having called cgif_addframe()
inkmeister opened this issue · comments
There appears to be a small memory leak when cgif_close is called without first adding a frame by calling cgif_addframe. It appears cgif_close will skip some cleanups when pGIF->CurResult is != CGIF_OK. In this case, it’s CGIF_PENDING and so pGIF doesn’t get freed within cgif_raw_close. I appreciate this isn’t the most typical use case for cgif, but it is possible for it to happen in my application if it has to close down before having had chance to add a frame. Thanks for a great library.
Hi @inkmeister. Thanks for pointing out this issue.
I've added a test case/fix for this in #41.
Hi Daniel,
No problem. Thanks for the quick turnaround.
Mark.
…________________________________
From: Daniel Löbl ***@***.***>
Sent: 06 February 2022 20:35
To: dloebl/cgif ***@***.***>
Cc: inkmeister ***@***.***>; Mention ***@***.***>
Subject: Re: [dloebl/cgif] Small memory leak when calling cgif_close() without having called cgif_addframe() (Issue #40)
Hi @inkmeister<https://github.com/inkmeister>. Thanks for pointing out this issue.
I've added a test case/fix for this in #41<#41>.
—
Reply to this email directly, view it on GitHub<#40 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALDTAO54ONAL4RNQFDCN6GDUZ3LRLANCNFSM5NVIVS6Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>