[v0.9.0][Windows] persistence=true crashes the indexing worker for repositories under CJK paths

[Akii-kawaii]

Version

codebase-memory-mcp 0.9.0

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

Summary

On Windows 11 x64 with the official v0.9.0 Windows amd64 standard binary, a clean full index of the public DeusData/codebase-memory-mcp repository succeeds from a CJK path when persistence=false, but the supervised worker exits nonzero when the same repository is indexed from the same CJK path with persistence=true.

An ASCII NTFS junction pointing to that exact CJK directory succeeds with persistence=true and writes .codebase-memory/graph.db.zst. The three-way result reproduced twice from clean project names, isolating the failure to persistence export for the non-ASCII path.

The failed run leaves a readable SQLite database (PRAGMA integrity_check = ok) and index_status reports ready, but the explicit index call returns exit_nonzero and no artifact is created.

Expected behavior

• A clean persistent index should work for a repository under a CJK path and write .codebase-memory/graph.db.zst.
• The canonical CJK path and an ASCII junction to the same directory should behave identically.
• If export fails, the response and worker log should expose the actual Windows path/file error.
• A failed explicit index should not be reported as ready without making the failed persistence state clear.

Query-phase CJK path behavior is tracked separately by #903 and is out of scope here.

Related: #400, #434, #903, and PR #891.

Reproduction

Environment

• OS: Windows 11 x64, build 10.0.26200
• PowerShell: 5.1.26100.8875; active code page: 936
• Binary: official v0.9.0 Windows amd64 standard release
• SHA-256: 9A205FA5AE759FBC866BFE1554F0C05A303BE9AE6E0A00F94D875DC0C25E0680
• Public repository: https://github.com/DeusData/codebase-memory-mcp.git
• Tag / commit: v0.9.0 / b637e3330c96cfe452da623db068c241aaa3ec01

Setup

$cbm = "$env:USERPROFILE\.local\bin\codebase-memory-mcp.exe"
$cjkRepo = Join-Path $env:LOCALAPPDATA 'Temp\cbm-持久化复现'
$asciiRepo = Join-Path $env:LOCALAPPDATA 'Temp\cbm-cjk-repro'

git clone --depth 1 --branch v0.9.0 --single-branch `
  https://github.com/DeusData/codebase-memory-mcp.git $cjkRepo
git -C $cjkRepo rev-parse HEAD
# b637e3330c96cfe452da623db068c241aaa3ec01

New-Item -ItemType Junction -Path $asciiRepo -Target $cjkRepo

Every scenario started with delete_project, so every index was a clean full run rather than an incremental run.

1. CJK path, persistence=false

$project = 'cbm-v090-public-cjk-pfalse-r2'
& $cbm cli delete_project --project $project
& $cbm cli index_repository --repo-path $cjkRepo --mode moderate --name $project --persistence false

Result: status=indexed, nodes=13007, edges=73886, skipped_count=0, artifact_present=false; SQLite integrity_check=ok; File nodes: 556.

2. Same CJK path, persistence=true

$project = 'cbm-v090-public-cjk-ptrue-r2'
& $cbm cli delete_project --project $project
& $cbm cli index_repository --repo-path $cjkRepo --mode moderate --name $project --persistence true

{"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.","repo_path":"%LOCALAPPDATA%\\Temp\\cbm-持久化复现"}

Result: worker exit 1; empty worker log; database integrity_check=ok; nodes=13007, edges=73864, File nodes 556; skipped_count not reported; artifact absent. index_status immediately returned ready.

3. ASCII junction to the same CJK directory, persistence=true

$project = 'cbm-v090-public-ascii-ptrue-r2'
& $cbm cli delete_project --project $project
& $cbm cli index_repository --repo-path $asciiRepo --mode moderate --name $project --persistence true

Result: status=indexed, nodes=13007, edges=73754, skipped_count=0, artifact_present=true; SQLite integrity_check=ok; File nodes 556; artifact 9,162,274 bytes, compression level 9, commit b637e3330c96cfe452da623db068c241aaa3ec01.

Repeated control matrix

Scenario	Run 1	Run 2
CJK, persistence=false	indexed; 13,007 nodes / 74,585 edges; skipped 0; no artifact; SQLite ok	indexed; 13,007 / 73,886; skipped 0; no artifact; SQLite ok
CJK, persistence=true	worker exit 1; 13,007 / 73,895; skipped not reported; no artifact; SQLite ok	worker exit 1; 13,007 / 73,864; skipped not reported; no artifact; SQLite ok
ASCII junction, persistence=true	indexed; 13,007 / 73,941; skipped 0; artifact 9,156,778 bytes; SQLite ok	indexed; 13,007 / 73,754; skipped 0; artifact 9,162,274 bytes; SQLite ok

The edge-count variation occurs across all three scenarios and is not used as the pass/fail criterion. The invariant signals are the worker exit status and artifact creation.

Workaround

Create an ASCII NTFS junction to the CJK repository directory, delete the old project, and run the full persistent index through the junction.

Logs

level=info msg=index.supervisor.reap outcome=exit_nonzero exit_code=1 signal=0
level=warn msg=index.supervisor.worker_failed outcome=exit_nonzero exit_code=1 log=%USERPROFILE%/.cache/codebase-memory-mcp/logs/.worker-42772.log
{"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.","repo_path":"%LOCALAPPDATA%\\Temp\\cbm-持久化复现"}

Referenced worker log:
%USERPROFILE%\.cache\codebase-memory-mcp\logs\.worker-42772.log
Length: 0 bytes

Failed database:
integrity=ok
nodes=13007
edges=73864
files=556
skipped_count=not reported in error JSON
artifact_exists=false

ASCII junction control:
level=info msg=index.supervisor.reap outcome=clean exit_code=0 signal=0
{"project":"cbm-v090-public-ascii-ptrue-r2","skipped_count":0,"nodes":13007,"edges":73754,"artifact_present":true,"status":"indexed"}

Diagnostics trajectory (memory / performance / leak issues)

Not applicable. This is a deterministic path- and persistence-dependent worker exit; no memory growth, hang, or leak was observed.

Project scale (if relevant)

Public repository at b637e33:1,818 tracked files; 556 indexed File nodes; 13,007 graph nodes; 73,754–74,585 graph edges across clean runs; 8 excluded directories; 0 skipped files on successful runs.

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.

[DeusData]

Thanks for the controlled CJK-path versus ASCII-junction matrix. This is now high priority in 0.9.1-rc under the Windows platform epic #394. The evidence isolates the persistent-artifact export path; the empty worker log and ready status after a failed persistence request are part of the bug, not separate cosmetic concerns.

[Akii-kawaii]

Thanks for the triage and for prioritizing this. I can retest any Windows build or PR against the same CJK-path versus ASCII-junction matrix and report the full results. Martin Vogel ***@***.***> 于2026年7月20日周一 06:48写道：

…

*DeusData* left a comment (DeusData/codebase-memory-mcp#1171) <#1171 (comment)> Thanks for the controlled CJK-path versus ASCII-junction matrix. This is now high priority in under the Windows platform epic #394 <#394>. The evidence isolates the persistent-artifact export path; the empty worker log and status after a failed persistence request are part of the bug, not separate cosmetic concerns. — Reply to this email directly, view it on GitHub <#1171?email_source=notifications&email_token=BQO4XMYOUOW3H2HMPIPM6HL5FVF3VA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBRG43DMNZSGM3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5017667236>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BQO4XM6ASDCRO3S5QYLXPKT5FVF3VAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNRWGEYDEMJUHA5US43TOVSTWNBZGIYTENRTHEYTDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BQO4XM5FXKY3OSUPWAIQD335FVF3VA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBRG43DMNZSGM3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/BQO4XM5JJPFCP6PS3LIMXY35FVF3VA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBRG43DMNZSGM3KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>