Worker continuously hangs and indexing process gives up eventually

[Skace-VI]

Version

codebase-memory-mcp 0.9.0

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

ui

What happened, and what did you expect?

codebase-memory-mcp cli index_repository --repo-path "D:\path\to\your\repo" --mode fast
level=info msg=mem.init budget_mb=32610 total_ram_mb=65220
level=info msg=index.supervisor.reap outcome=hang exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=hang exit_code=1 log=C:/Users/lwu/.cache/codebase-memory-mcp/logs/.worker-25072.log
level=info msg=index.supervisor.reap outcome=hang exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=hang exit_code=1 log=C:/Users/lwu/.cache/codebase-memory-mcp/logs/.worker-25072.log
level=info msg=index.supervisor.reap outcome=hang exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=hang exit_code=1 log=C:/Users/lwu/.cache/codebase-memory-mcp/logs/.worker-25072.log
level=warn msg=index.file_quarantined path=vi.mdf.nodsl.modeling.if/src/aquintos/mdf/dblayer/NullDynamicLoadService.java outcome=hang attempt=2
level=info msg=index.supervisor.reap outcome=hang exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=hang exit_code=1 log=C:/Users/lwu/.cache/codebase-memory-mcp/logs/.worker-25072.log
level=warn msg=index.file_quarantined path=aquintos.metric.engine/src/aquintos/metric/engine/creation/MetricModelCreationConstants.java outcome=hang attempt=3
level=info msg=index.supervisor.reap outcome=hang exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=hang exit_code=1 log=C:/Users/lwu/.cache/codebase-memory-mcp/logs/.worker-25072.log
level=warn msg=index.file_quarantined path=aquintos.analyse.problemview/src/aquintos/analyse/problemview/views/AnalyseProblemView.java outcome=hang attempt=4
level=info msg=index.supervisor.reap outcome=hang exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=hang exit_code=1 log=C:/Users/lwu/.cache/codebase-memory-mcp/logs/.worker-25072.log
level=warn msg=index.file_quarantined path=aquintos.metric.engine/src/aquintos/metric/engine/util/Messages_de.properties outcome=hang attempt=5
level=info msg=index.supervisor.reap outcome=hang exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=hang exit_code=1 log=C:/Users/lwu/.cache/codebase-memory-mcp/logs/.worker-25072.log
level=warn msg=index.supervisor.unattributable action=give_up
level=info msg=index.supervisor.reap outcome=hang exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=hang exit_code=1 log=C:/Users/lwu/.cache/codebase-memory-mcp/logs/.worker-25072.log
{"status":"error","outcome":"hang","hint":"Indexing worker timed out (a file made no progress). The worker was terminated and the server survived. Re-run to retry.","repo_path":"D:\path\to\your\repo"}

This was run on a 350.57MB folder. It seems only not to be working in this specific subfolder. The files it hangs on are seemingly unrelated and quarantined files change between runs. It also does not seem to be related on size as a neighbouring folder (270MB) indexed successfully within a minute. Worker logs are completely empty.

Reproduction

codebase-memory-mcp cli index_repository --repo-path "D:\path\to\your\repo" --mode fast

I can't share the repository because it is proprietary. I unfortunately was not able to create a dummy project that triggers the same bug. I tried the indexing process on the two biggest subfolders (that contained files being quarantined) within the failing folder and both finished successfully.

The indexing process was run on a folder within a Java/Eclipse RCP project with 350.57MB in size on Windows 11.

Logs

Worker logs were completely empty

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.

[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 detailed containment log. The changing quarantine candidates and successful indexing of the individual subfolders suggest a repository-level progress or supervision problem rather than one deterministic Java file.

Please attach the output of index_status after the failed run, the total discovered file count, whether this root is a Git working tree, and a directory-level file-count breakdown for the top-level modules. If possible, retry only with a diagnostic v0.9.1 build once one is available; the current zero-byte worker log is itself part of the stability gap tracked in #1132. Marking awaiting-reporter for those non-proprietary diagnostics while keeping this in 0.9.1-rc.