fix: the access logger no longer keeps its instance alive #19

Merged

KofTwentyTwo merged 1 commits from feature/access-log-lifecycle into develop

2026-10-16 16:41:28 +00:00

Author	SHA1	Message	Date
james.maesandClaude Opus 5.5	325150a938	fix: the access logger no longer keeps its instance alive The worker thread's task and the JVM shutdown hook referenced the logger (and through it the QInstance) strongly for the life of the JVM, so every instance a host or test built and dropped stayed in memory (kof22's suite ran out of heap in CI). Both now hold the logger weakly: a dropped instance can be collected and its worker stops at the next tick. - withRegisterShutdownHook(false) for hosts that close the runtime themselves (default true, unchanged behaviour). - isWorkerRunning() for hosts and tests. - README and CHANGELOG (also notes #18). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-16 11:39:12 -05:00

Author

SHA1

Message

Date

james.maesandClaude Opus 5.5

325150a938

fix: the access logger no longer keeps its instance alive

The worker thread's task and the JVM shutdown hook referenced the logger
(and through it the QInstance) strongly for the life of the JVM, so every
instance a host or test built and dropped stayed in memory (kof22's suite
ran out of heap in CI). Both now hold the logger weakly: a dropped
instance can be collected and its worker stops at the next tick.

- withRegisterShutdownHook(false) for hosts that close the runtime
  themselves (default true, unchanged behaviour).
- isWorkerRunning() for hosts and tests.
- README and CHANGELOG (also notes #18).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-16 11:39:12 -05:00