Hunting down a C memory leak in a Go program (2021)

This isn’t a memory leak though, is it?

I think the general solution to avoid this kind of stuff is providing your own memory allocation functions to libraries (don’t know if this library supports that). That way one can limit, track and isolate memory allocations.