<b>3.0.15.33897</b>
Gabriele Ciech 2026.10.30 11:36:19
Fix double decrUsage of current extent in FreeObjects::newBlock() on allocation failure
When newExtent() throws (e.g. std::bad_alloc), the current extent has already
been retired with decrUsage() but currentExtent still points to it, so the next
call retires it again. Its usage count drops below the number of live blocks
and the extent (and the medium hunk holding it) can be reclaimed while still
in use, leading to crashes in unlinkBlocks()/SemiDoubleLink::remove().
Allocate the new extent first and retire the old one only after success.
Backport of #9250.

Changed paths:
  M src/common/classes/alloc.cpp