Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Windows: index worker crashes (0xC0000005) in parallel.extract on whole mixed C#/Vue repo; each sub-folder indexes fine alone

未关闭
  • 哪里不对？
#2,785 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c, csharp, javascript, markdown, sql
领域
backend, devtools, performance

调研方向

Start by tracing the index_repository CLI entry point into parallel.extract and inspect the worker crash and allocator diagnostics on Windows. The report gives no source files or tests to start from, so first determine how to capture a crash dump or enable extract phase tracing. Done means the reported whole repository indexes successfully on Windows while its subfolders continue to index successfully.

由索引模型根据 Issue 内容生成。

描述

bug stability/performance windows

Summary

On Windows, index_repository on a mixed C# / Vue / JS / Markdown / SQL repo (~990 files after ignores) ends with index worker ended with crash (exit=-1073741819) (0xC0000005, access violation) during parallel.extract. Every top-level sub-folder of the same repo indexes fine on its own; only the whole-repo index crashes. This looks similar in shape to #2349 (each package alone is fine, only the union crashes), but the signature differs: Windows, access violation, extract phase.

Environment

  • codebase-memory-mcp 0.12.1 (install.ps1, --skip-config, checksum verified)
  • Windows 11 Pro 10.0.26300, amd64
  • Repo: .NET Framework 4.8 solution (ASP.NET WebForms + WebApi, several C# projects), Vue 2 single-file components without a bundler, plain JS/CSS, SQL scripts, Markdown docs. Private repo, so I can't attach it.

What I ran

codebase-memory-mcp cli index_repository --repo-path <repo root>, with and without --mode fast.

Result

Attempt Outcome
default mode worker crash, exit=-1073741819
--mode fast same crash
--mode fast + CBM_INDEX_SINGLE_THREAD=1 same crash
--mode fast + CBM_WORKERS=1 + CBM_INDEX_SINGLE_THREAD=1 same crash
each top-level folder indexed separately (5 .NET/web projects, plus docs, Database, specifications, tooling dirs, hidden dirs) all succeed

Notes:

  • The files that were started but not finished when the worker died differ between runs, so I don't think one specific file triggers it.
  • The two env vars come from strings in the binary, not from the docs. The worker log still shows parallel.extract after setting them, so they may be no-ops here.
  • The first lines of stderr are always mem.allocator.preloading_completed still_preloading=false detail=allocator_was_still_preloading,_so_arena_creation_and_purging_were_disabled. Not sure if related.
  • Last log lines before the crash are parallel.extract.file.start ... / ...file.done ... / parallel.extract.progress done=N total=M, with N around 110 to 150 of ~990 to ~1190 depending on the ignore set.

Expected

The whole-repo index completes, as each part does alone.

Questions

  • Is there a supported way to get a crash dump or a more verbose extract-phase trace on Windows (CBM_DIAGNOSTICS?) that I can attach?
  • Is a Windows-specific allocator/arena problem under parallel.extract a known thing?
主要语言
C
星标
45.8k
派生
3.8k
平均合并
3 天 6 小时
30 天内合并 PR
201

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

DeusData/codebase-memory-mcp 的其他 Issue

查看 DeusData/codebase-memory-mcp 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。