gpac v2.2.1 was discovered to contain a memory leak via the gfio_blob variable in the gf_fileio_from_blob function.
Memory leak in function [gf_fileio_from_mem](https://github.com/gpac/gpac/blob/941a0891b989f5ad86b739cfb12c84b7e62e8ee4/src/utils/os_file.c#L1447)
The memory leak is reported by a static analyzer tool developed at CAST (https://www.linkedin.com/company/cast-center).

Dynamic memory is allocated [here](https://github.com/gpac/gpac/blob/941a0891b989f5ad86b739cfb12c84b7e62e8ee4/src/utils/os_file.c#L1450) if `gf_fileio_new` fails, function will return from [here](https://github.com/gpac/gpac/blob/941a0891b989f5ad86b739cfb12c84b7e62e8ee4/src/utils/os_file.c#L1455) and allocated memory will remain not freed.
Memory leak in function gf_fileio_from_mem
This is a GitHub Issue
repo:gpac
owner:gpac
Title : Memory leak in function gf_fileio_from_mem
Issue date:

--- start body ---
Memory leak in function [gf_fileio_from_mem](https://github.com/gpac/gpac/blob/941a0891b989f5ad86b739cfb12c84b7e62e8ee4/src/utils/os_file.c#L1447)
The memory leak is reported by a static analyzer tool developed at CAST (https://www.linkedin.com/company/cast-center).

Dynamic memory is allocated [here](https://github.com/gpac/gpac/blob/941a0891b989f5ad86b739cfb12c84b7e62e8ee4/src/utils/os_file.c#L1450) if `gf_fileio_new` fails, function will return from [here](https://github.com/gpac/gpac/blob/941a0891b989f5ad86b739cfb12c84b7e62e8ee4/src/utils/os_file.c#L1455) and allocated memory will remain not freed.
--- end body ---

A memory leak in the function gf_fileio_from_mem of GPAC can lead to increased memory usage over time, potentially affecting application performance and stability. The leak occurs when dynamic memory is allocated but not freed if the gf_fileio_new function fails, resulting in unreferenced memory that is not reclaimed.