Repository navigation
Crash when indexing a repository #347
Description
Faulting application name: codebase-memory-mcp.exe, version: 0.0.0.0, time stamp: 0x69f91461
Faulting module name: codebase-memory-mcp.exe, version: 0.0.0.0, time stamp: 0x69f91461
Exception code: 0xc0000005
Fault offset: 0x0000000000c901aa
Faulting process id: 0x0x84B4
Faulting application start time: 0x0x1DCE32F257A01A6
Faulting application path: C:\Users\akash.singh\AppData\Local\Programs\codebase-memory-mcp\codebase-memory-mcp.exe
Faulting module path: C:\Users\akash.singh\AppData\Local\Programs\codebase-memory-mcp\codebase-memory-mcp.exe
Report Id: ccf5ec7e-a7a1-406e-a7ed-b651c5ba3a8d
Faulting package full name:
Faulting package-relative application ID:
The repository is quite large. I tried on a small repository (a different one) and it works.
There are some very large files in repo, but the code size is far smaller than the linux os source code.
Activity
akash02hexagon commentedon May 13, 2026
PS C:\Users\akash.singh\Projects> codebase-memory-mcp cli --progress index_repository '{"repo_path": "C:\Users\akash.singh\Projects\myproj"}'
level=info msg=mem.init budget_mb=16228 total_ram_mb=32456
Discovering files (9202 found)
Starting full index
[1/9] Building file structure
Extracting: 644/9202 files (7%)
PS C:\Users\akash.singh\Projects>
So it crashes midway. I then found the folder (which has subfolders and no files) from where it crashes.
But if re-run the same command for each subfolder in that folder then there are no crashes.
akash02hexagon commentedon May 13, 2026
The crash comes in at random progress, but early, so anywhere between %5 to 35%.
lichaoren commentedon May 22, 2026
I'm experiencing the same issue from the latest release, 0.6.1. It's able to index a sub folder of the repo...
I used to use the codebase-memory-mcp extension in vs code, and it worked, taking 12min to index.
couldn't pipe any useful log
please help windows user! 🤟
lichaoren commentedon May 22, 2026
Observations:
src/service/— 3,500 files, completes successfully).cbmignorereducing file count from 8,400 → ~5,500 did not prevent the crashmode: fastvia MCP also crashes (same exit code)This looks like a race condition or use-after-free in the parallel extraction pipeline rather than a single-file parser crash, since the crash point varies slightly and individual subdirectories index fine.
lichaoren commentedon May 26, 2026
level=iEXIT=-1073741819
same codebase indexed in an Ubuntu WSL also gets
lichaoren commentedon May 26, 2026
with worker == 1, the crash was always delayed to the last file
and worker > 2, it crashes immediately after start
ci(temp): Windows repro harness for #394 group
DeusData commentedon May 31, 2026
Verified fixed on v0.7.0. I indexed a repo at a Windows
C:\drive-letter path in CI (run) and it completed cleanly (INDEX_EXIT=0,status:indexed, 9 nodes) — no0xc0000005. The Windows wide-char path migration (#386) plus the C/C++ extraction crash fixes (#215/#312/#360) resolved the indexing crash. Closing; please reopen with a fresh Windows crash dump if it recurs on v0.7.0. 🙏ci: remove temporary Windows repro harness