OpenHFT/Chronicle-Core chronicle-core-2026.4

chronicle-core: 2026.4

on GitHub

[CORE-62] Updates to Chronicle Core required, update to Bytes as a defensive change

[CORE-61] Add initial @address semantics assertion layer for hardening

[CORE-60] Refactor CleaningThreadLocal.cleanupNonCleaningThreads() to release the static registry lock before running user-provided cleanup callbacks. Drain stale entries into a pending-callbacks list under the lock; execute callbacks afterwards, outside the lock. This prevents slow or user-defined cleanup code from blocking unrelated CleaningThreadLocal operations like set(), remove(), and initialValue() across the JVM. Previously, cleanup occurred while removing stale entries from the shared cleaningThreadLocals collection. Since cleanup callbacks are user-provided and may be slow, blocking, or interact with other Chronicle resources, holding the global registry lock during cleanup posed unnecessary risks.