We have a continuously running process saving files to HDF5 and, in some circumstances, it happens that the HDF5 garbage collector grows indefinitely, aka never collecting, and that leads to OOM. We have fixed the situation by calling
H5garbage_collect on a regular basis, but any additional informations on how the garbage collection works and what is collected would be appreciated.
Moreover, this a new problem to us, is there any recent change that could have affected the way the garbage collection works? Or is there any known usage pattern that could lead to this behavior?
We have not investigated yet whether it is a regression (v1.10.4 is used).