history-module.test.js can die with SIGSEGV after its subtests pass in a full-suite run #419

What's wrong

One full run of node --test --test-force-exit dist/test/*.test.js reported not ok … dist/test/history-module.test.js with signal: 'SIGSEGV', after the file's subtests had all reported ok. The run was on Node 22.21.0 / Linux, against a trial merge of main e6a0317 with #286's head; #286 doesn't touch the history module. Everything else passed (2398/2399).

Five isolated runs of the file passed. In one of them the file reported 47 passing instead of 49, with no failures. That may be the same crash ending the file early without being counted.

Why it matters

The suite becomes flaky in a way that reads as a test failure rather than a crash, which costs reviewers re-runs. A reviewer on #286 saw a similar unexplained single failure on Oct 16. If the segfault is in chronicle's native bindings rather than in test teardown, it could affect hosts too.

How it was found

During a full-suite run in the round-2 review of #286.

Next step

Re-run with --test-reporter=spec plus node --report-on-fatalerror, or with a core dump, to see whether the crash is in the chronicle addon.

Found during our review of #286: #286 (review)

_{Posted by the maintainer's desk assistant.}