From: Tim W. <sou...@wo...> - 2025-05-03 15:49:53
|
Hi everyone, I've pushed 0.4b52 today. This is a minor release that fixes all the remaining issues that valgrind reports. There was nothing major, the vast majority were memory that wasn't freed before the program exits. A few minor memory leaks, one read beyond the end of a buffer (but the value read wasn't used) and some uninitialized memory reads where structures are written to tape. I have changed the way the workers communicate while writing to tape. I wasn't able to work out why but the previous method of synchronizing the workers didn't work reliably under valgrind and regularly lead to corrupted tapes where data was written out of order. This change shouldn't cause any differences or problems but if you do see problems with this release - most likely related to dump locking up and never completing - then this change is likely the culprit. Tim. |