Memtrace v1.1.11

Memtrace v1.1.11

A second Ctrl-C no longer strands the sidecars; a Cortex owner stops only its own store's daemon

New

• New features land on Nightly first: npm install -g memtrace@nightly is the same memtrace command, and it is not always stable. They still ship on the default install. memtrace install stays on the channel you already have.

Fixed

• A second Ctrl-C during shutdown used to leave the database sidecar and the Cortex daemon running until the next memtrace stop, start, or doctor --fix: the second press exits the owner immediately, before its shutdown reaches the sidecars, and macOS ties no child to its parent. The owner now hands every sidecar it recorded a termination signal on that immediate exit, from the signal handler itself, so one press or two both end with nothing left behind; whatever ignores the signal is still closed from the ledger by the next stop.
• A Memtrace owner or MCP session that had just claimed its Cortex store used to stop every Cortex daemon on the machine before starting its own, including daemons serving other stores (a second MEMCORTEX_STORE_DIR on the same machine, for instance), whose owners then restarted them. It now stops only daemons whose command line names its own store, and leaves alone any process whose command line it cannot read.

Install

npm install -g memtrace