Bug
Running ctx-upgrade installs the new plugin version and starts a new server process, but never terminates the old server process. Both versions run concurrently after every upgrade.
Reproduction
- Note the running node processes:
ps aux | grep context-mode
- Run
ctx-upgrade
- Check processes again — old version (
1.0.x/start.mjs) is still alive alongside the new one
Impact
Each upgrade leaks a server process. If the user upgrades multiple times in a session (e.g. troubleshooting), multiple zombie instances accumulate. In combination with the WAL contention bug (see related issue), this caused a 238MB WAL file and every ctx_search call hanging indefinitely.
Expected behaviour
ctx-upgrade should send SIGTERM (or equivalent on Windows) to the currently running server before starting the new one.
Environment
- Platform: Windows 11
- Claude Code plugin
- context-mode v1.0.125 → v1.0.127
Bug
Running
ctx-upgradeinstalls the new plugin version and starts a new server process, but never terminates the old server process. Both versions run concurrently after every upgrade.Reproduction
ps aux | grep context-modectx-upgrade1.0.x/start.mjs) is still alive alongside the new oneImpact
Each upgrade leaks a server process. If the user upgrades multiple times in a session (e.g. troubleshooting), multiple zombie instances accumulate. In combination with the WAL contention bug (see related issue), this caused a 238MB WAL file and every
ctx_searchcall hanging indefinitely.Expected behaviour
ctx-upgradeshould send SIGTERM (or equivalent on Windows) to the currently running server before starting the new one.Environment