summaryrefslogtreecommitdiffstats
path: root/test/ttsafe_cancel.c
diff options
context:
space:
mode:
authorjhendersonHDF <jhenderson@hdfgroup.org>2024-01-23 16:21:59 (GMT)
committerGitHub <noreply@github.com>2024-01-23 16:21:59 (GMT)
commitf86fe61c7f6fa43cc16d555f9c925e43baa3de8f (patch)
treecd51adf099e654b280297a184e7a3480dc8d8ed8 /test/ttsafe_cancel.c
parent7e48d4f767f1cea64b7642db39a9d38c2c2eda13 (diff)
downloadhdf5-f86fe61c7f6fa43cc16d555f9c925e43baa3de8f.zip
hdf5-f86fe61c7f6fa43cc16d555f9c925e43baa3de8f.tar.gz
hdf5-f86fe61c7f6fa43cc16d555f9c925e43baa3de8f.tar.bz2
Remove cached datatype conversion path table entries on file close (#3942)
Remove cached datatype conversion path table entries on file close When performing datatype conversions during I/O, the library checks to see whether it can re-use a cached datatype conversion pathway by performing comparisons between the source and destination datatypes of the current operation and the source and destination datatypes associated with each cached datatype conversion pathway. For variable-length and reference datatypes, a comparison is made between the VOL object for the file associated with these datatypes, which may change as a file is closed and reopened. In workflows involving a loop that opens a file, performs I/O on an object with a variable-length or reference datatype and then closes the file, this can lead to constant memory usage growth as the library compares the file VOL objects between the datatypes as different and adds a new cached conversion pathway entry on each iteration during I/O. This is now fixed by clearing out any cached conversion pathway entries for variable-length or reference datatypes associated with a particular file when that file is closed.
Diffstat (limited to 'test/ttsafe_cancel.c')
0 files changed, 0 insertions, 0 deletions