Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#2,785 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
c, csharp, javascript, markdown, sql
Bereich
backend, devtools, performance

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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?
Vorherrschende Sprache
C
Sterne
45.8k
Forks
3.8k
Ø Merge
3 T. 16 Std.
Gemergte PRs (30 T.)
203

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus DeusData/codebase-memory-mcp

Alle Issues in DeusData/codebase-memory-mcp

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.