Opened 6 years ago
Closed 6 years ago
#7191 closed enhancement (worksforme)
The gdal HDF5 driver is not thread safe
| Reported by: | TimLander | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | default | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: |
Description
This is a know issue in hdf5, however my software currently cannot support hdf5 through gdal due to this.
Change History (3)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
I cannot reproduce any thread-safety issue with GDAL and HDF5 on Ubuntu 16.04 (libhdf5 1.8.16) when using the test program multireadtest. Looking at calls, I see libhdf5 use mutexes internally. Can you explain more the thread-safety issues you get (operating system, libhdf5 version, test dataset, etc.) ?
comment:3 by , 6 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Closing due to lack of feedback from reporter. Re-open if you can provide more elements
Note:
See TracTickets
for help on using tickets.
Note that in the mean time you still have the possibility to wrap GDAL calls with a mutex in your own code. The way the issue would be resolved in GDAL would be to add a mutex in the HDF5 driver, like done in the HDF4 driver