Open eduardo-camargo opened 2 years ago
Reference: Forum thread memory backed files
Hi @gheber. Hope everything is good on your side. I was hoping to get some info on this issue. Do you have any timeline to fix this? I'm just trying to get an idea when this might be resolved so I can plan accordingly on my side.
I'm sorry @eduardo-camargo, no timeline yet. (Our engineers were busy getting 1.13.2 out the door.) I'll keep you posted.
@derobins and @gheber do you have any updates on this? Maybe the fix has been incorporated into one of the new versions? If so, could you point to a specific commit?
Hello @gheber and @derobins. I saw there was some movement here and would like to ask if there is any fix/workaround for this issue. Thanks.
Hello @gheber and @derobins. I saw there was some movement here and would like to ask if there is any fix/workaround for this issue. Thanks.
We're trying to work through our backlog and tagging / assigning issues is a part of that, but we haven't made any specific movement on this bug yet. Good to know you are still interested, though! I'll see what I can do to get this into the fall releases.
Hi @derobins and @gheber just wanted to follow up on this issue to see if there are any updates
Hello, we encountered issues using in-memory hdf5 as well in the context of h5py, which might be caused by the same underlying issue. See the post about it on the hdf group forum. Looking forward to trying it out in 1.14.4.
With the first releases for 1.14.4 trickling, what are the chances that his issue will be resolved in the near future?
I am having trouble to set up an image into a memory backed file. I’d like to set up a memory file, copy some data into it and then extract the a file image which will be set in another memory backed file (this last step seems to be the issue). The only way I found to make this work is to relaxing the version bounding to the earliest (H5F_LIBVER_EARLIEST).
Here it is the code that reproduces the issue. There is no buffer copy over network, everything is running on a single machine (Red Hat Enterprise Linux Server 7.9). File used to replicate the issue (file_image_core_test.h5) can be found on the HDF5-1.12.1 repo test folder. I would like to stress the below code works fine as is when using HDF5-1.8.17 but breaks on the second H5Fopen call when using HDF5-1.12.1. To make the code work again I need to change the first H5F_LIBVER_LATEST by H5F_LIBVER_EARLIEST on H5Pset_libver_bounds(..., H5F_LIBVER_EARLIEST, H5F_LIBVER_LATEST); which introduces a humongous slow down. The exact same issue happens on HDF5-1.12.2.
This bug report was originated from a discussion on HDF Forum. [(https://forum.hdfgroup.org/t/memory-backed-files/9878)]