Closed TomAugspurger closed 12 months ago
Hmm, seems like cfgrib.Message
might free the memory when it goes out of scope at https://github.com/ecmwf/eccodes-python/blob/88ce860383f60afeb34119a31886d5a2e684d767/eccodes/highlevel/message.py#L28 by calling codes_release
. So we shouldn't need to / can't call it too.
Closing this until I have a better idea what's going on :/
I'm trying to track down what looks like a memory leak in a process using kerchunk. By 26,000 calls to
scan_grib
, memory usage in the process had grown from ~150 MB to ~2800 MB.I see that
eccodes
has acodes_release
function. Is anyone more familiar with GRIB (@dcherian maybe?) know if we should be calling that? My initial tests are just segfaulting :/In case it matters, I'm using this as an example, using this branch for stactools.ecmwf_forecast: