Index Error: outcome=killed exit_code=-1 signal=9

[lindeer]

Version

codebase-memory-mcp 0.9.0

Platform

Linux (arm64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

codebase-memory-mcp-linux-arm64-portable-0.9.0.tar.gz

codebase-memory-mcp cli index_repository --repo-path /path/to/my/code
level=info msg=mem.init budge_mb=1989 total_ram_mb=7957
level=info msg=index.supervisor.reap outcome=killed exit_code=-1 signal=9
level=info msg=index.supervisor.workder_failed outcome=killed exit_code=-1 log=~/.cache/codebase-memory-mcp/logs/.worker-13534.log
level=info msg=index.supervisor.reap outcome=killed exit_code=-1 signal=9
level=info msg=index.supervisor.workder_failed outcome=killed exit_code=-1 log=~/.cache/codebase-memory-mcp/logs/.worker-13534.log
{"status":"error","outcome":"killed","hint":"Indexing worker crashed on a file. The crash was contained (the server survived). Re-run to retry; a future release isolates the culprit file.","repo_path":"/home/admin/Work/dev/code"}

Reproduction

codebase-memory-mcp cli index_repository --repo-path /path/to/my/code
level=info msg=mem.init budge_mb=1989 total_ram_mb=7957
level=info msg=index.supervisor.reap outcome=killed exit_code=-1 signal=9
level=info msg=index.supervisor.workder_failed outcome=killed exit_code=-1 log=~/.cache/codebase-memory-mcp/logs/.worker-13534.log
level=info msg=index.supervisor.reap outcome=killed exit_code=-1 signal=9
level=info msg=index.supervisor.workder_failed outcome=killed exit_code=-1 log=~/.cache/codebase-memory-mcp/logs/.worker-13534.log
{"status":"error","outcome":"killed","hint":"Indexing worker crashed on a file. The crash was contained (the server survived). Re-run to retry; a future release isolates the culprit file.","repo_path":"/home/admin/Work/dev/code"}

Logs

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

[MSV1971]

Possibly related data point, different platform: I hit the same index.supervisor.worker_failed message family on Windows (x64), v0.9.0, native binary, but with exit_code=1 (no signal) rather than signal=9, so it may or may not share the same root cause as the Linux/arm64 report above.

• Upgraded a working v0.8.1 install to v0.9.0 (checksum + SLSA verified before swap).
• A scheduled incremental reindex of a local mid-size repo (~4800 nodes / ~10700 edges at the 0.8.1 baseline) then failed 100% of the time — a scheduled task retried it every 20 minutes for ~30 hours straight, every single attempt failed the same way.
• No culprit file was ever identified in the output.
• The worker log referenced in the worker_failed message was empty (0 bytes) every time — no stack trace, nothing to point at a cause. That alone might be worth a look: crash logging doesn't seem to be capturing anything on this failure path, at least on Windows with exit_code=1.
• Rolling back to v0.8.1 (same repo, same machine, only the binary changed) immediately restored successful reindexing (~0.3s, 4834 nodes, healthy).

I don't have a shareable minimal repro (private repo, and since the logs were empty I can't even point at which file triggers it), so I'm not filing a separate issue per the bug report template's requirement for shareable repro — just flagging in case the empty-log behavior or the Windows/exit_code=1 variant of this crash is useful signal for triage here. Happy to try anything diagnostic (e.g. CBM_DIAGNOSTICS=1) on request if it would help.

[JA-Developer]

In my case, I got the same message in Windows:

{"status":"error","outcome":"exit_nonzero","hint":"Indexing worker crashed on a file. The crash was contained (the server survived). Re-run to retry; a future release isolates the culprit file."}

And the problem was beause I was not escaping quotes in CMD. I solved it using:

codebase-memory-mcp cli index_repository "{"repo_path": "C:\Users\LENOVO\source\repos\Project"}"

[github-actions]

Thanks for the report! To move this forward we need a bit more so we can reproduce it ourselves:

• the codebase-memory-mcp --version you're on
• the exact steps or command you ran
• a public repo (or a small dummy snippet) that shows the problem — please don't paste proprietary code

Once that's here we'll pick it straight back up. Heads-up: issues left awaiting-reporter are automatically closed after a few weeks of silence, but a comment reopens the door anytime.

[DeusData]

Thanks for the report. This remains a high-priority 0.9.1-rc worker-crash issue. Please attach the referenced worker log, the exact Linux arm64 command or JSON argument form, repository file count and main languages, and whether the same path succeeds in fast mode. The Windows quoting workaround reported in the comments may be a separate invocation issue, so marking awaiting-reporter for the original Linux evidence.