https://github.com/zlib-ng/minizip-ng/blame/d69cb0a5392332d6a55e9b56405a6fa2fc8b157d/mz_zip.c#L1501
Greetings! I have used static analyzer tools on this repo. and it reported interesting thing - > potential leak on the specified line.
If i understand the logic of mz_stream_mem = we should clean our resources after allocation with mz_stream_mem_delete() passing it same stream we passed to mz_stream_mem_open. I believe this function is called when given example on how to use streams (README.md), but 1f we take a look at function unzFile unzOpen_MZ(void *stream) in mz_compat.c = it's not the case.
Please, verify if this issue is a real leak or not, and if any actions should be made to prevent it.
https://github.com/zlib-ng/minizip-ng/blame/d69cb0a5392332d6a55e9b56405a6fa2fc8b157d/mz_zip.c#L1501
Greetings! I have used static analyzer tools on this repo. and it reported interesting thing - > potential leak on the specified line.
If i understand the logic of mz_stream_mem = we should clean our resources after allocation with mz_stream_mem_delete() passing it same stream we passed to mz_stream_mem_open. I believe this function is called when given example on how to use streams (README.md), but 1f we take a look at function
unzFile unzOpen_MZ(void *stream)in mz_compat.c = it's not the case.Please, verify if this issue is a real leak or not, and if any actions should be made to prevent it.