Skip to content

Memtrace v1.1.3

Choose a tag to compare

View all tags
@Alex793x Alex793x released this 13 Aug 12:44
· 2 commits to main since this release
v1.1.3
6f9acf6

Memtrace v1.1.3

An editor session connects instead of pegging the CPU

Fixed

  • Opening Memtrace from Cursor or Claude no longer grabs every fast core on the machine. Each chat used to start a full-speed copy of the indexer, so a few open sessions drove idle CPU into the nineties and then the editor gave up waiting for tools. Those sessions now stay small. If yours is already stuck, reload the Memtrace MCP server after upgrading.
  • A second editor session can join a Memtrace that is still starting, instead of dying with a closed connection and launching yet another copy. The first session used to keep its address unpublished until the database finished opening, which is slow, and every retry piled on.
  • A session that joined an already-running Memtrace no longer starts its own file watcher or background Cortex process. That second copy was competing for the same store, which is part of why idle CPU climbed and tools flapped.

Install

npm install -g memtrace
Assets 4
Loading