Ward Fisher

I've just checked the documentation for `h5allocate_memory()`, it was introduced in HDF5 1.8.15. So you'll need to bump up to that version at least, and I will correct our documentation.

I mean, it depends what libraries are linked against it, which can be tricky. If it's only netCDF, you can upgrade in place and reconfigure/recompile netCDF from source (or, compile...

Thanks; taking a look at this now.

Thanks; I'm able to recreate this, and have updated the code you provided to show this in real time via calls to `getrusage`. I'll see if I can figure out...

Ok, so I while I try to formulate my thoughts around this (and the related issues), I believe that the problem might be out of our hands. The last step...

Further, if the issue is around the handling of the libhdf5 objects, it is non-obvious; the same tests using other storage formats (netCDF3, ncZarr) do not exhibit the same growing...

Playing around with this some more, it feels like there might be a dangling open resources when an HDF5 is being closed. I should be able to follow up on...

The failures are unrelated to the PR, and are part of an issue we're fixing on the Unidata side. This looks good and will be merged shortly.

Thank you @alexandervladsemenov! That is very helpful, a great illustrative example. As an aside, our system folks are on guard for anything that looks like a secret key being posted...

This is not an uncommon feature request, and is one that definitely requires a broader discussion within the user community (and internally) regarding the technical debt Unidata would be incurring....