Skip to content

task: Stability — crashes, segfaults, and memory safety during indexing (14 issues) #390

Open
3 of 9 issues completed

Description

@DeusData

Scope

Umbrella tracker for crashes, segfaults, and memory-safety failures during indexing. Clusters: C/C++ LSP template-call resolution, lsp_cross scale limits, parallel-extract on very large repos, and dump-phase crashes.

Sub-issues

Fixed in v0.7.0:

Awaiting v0.7.0 retest (old-version crashes; not reproducible without reporter's exact repo):

Status (2026-05-31)

The crash classes are addressed in v0.7.0 by an extensive hardening pass: C-LSP template-call guards (#322/#323/#360), lsp_cross scale fixes (#340/#344), a deadlock/ordering fix (82d5c84), and fixed-size-stack → dynamic conversion (#339). ~11 children fixed/closed. The 6 remaining opens are crashes reported on v0.5.7–v0.6.1 against massive or proprietary repos (AOSP, 1.42M-line Java, private monorepos) that can't be cloned for CI repro — each has a targeted v0.7.0 retest request asking for the specific crashing file/path or log so a direct regression test can be added.

Acceptance

  1. No crash on the regression corpus (icinga2, kicad, xxhash, scale-synthesized def sets). ✅
  2. lsp_cross handles large def sets without SIGSEGV. ✅ (Segmentation fault at start of lsp_cross pass on repositories with 200+ files #340/SIGSEGV in lsp_cross pass when all_defs exceeds ~1189 entries (scale-dependent, not file-specific) #344)
  3. Remaining large-repo crashes confirmed fixed or reproduced via reporter-supplied minimal cases — pending v0.7.0 retests.

Why one task

These share memory-safety / scale infrastructure in the extraction + lsp_cross + dump pipeline.

Added 2026-06-29 (triage)

Added 2026-06-30 (triage)

Added 2026-07-09 (triage)

Added 2026-08-03 (triage)

Activity

  1. added
    bugSomething isn't working
    stability/performanceServer crashes, OOM, hangs, high CPU/memory
    taskUmbrella task grouping multiple related issues
    on May 30, 2026
  2. DeusData commented on May 30, 2026

    @DeusData
    OwnerAuthor

    Stability triage pass complete (14/14 children)

    Worked each child by reproducing first (test or real-repo index), then confirming the fix:

    ✅ Resolved with regression tests (5):

    ✅ Resolved by real-repo reproduction in CI (2):

    💬 Could not reproduce on v0.7.0 — asked reporters to retest / provide data, left open (7):

    All fixes verified under -fsanitize=address,undefined. The bulk of this group was resolved by the v0.7.0 C/C++ extraction hardening (#215/#312/#360), growable AST stacks (#339), the cross-LSP rewrite (#340/#344), and WAL/cgroup fixes (#277/#363).

  3. added
    priority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.
    on Jun 30, 2026
  4. added this to the 0.9.1-rc milestone on Jul 8, 2026
  5. added
    parsing/qualityGraph extraction bugs, false positives, missing edges
    ux/behaviorDisplay bugs, docs, adoption UX
    windowsWindows-specific issues
    on Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingparsing/qualityGraph extraction bugs, false positives, missing edgespriority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.stability/performanceServer crashes, OOM, hangs, high CPU/memorytaskUmbrella task grouping multiple related issuesux/behaviorDisplay bugs, docs, adoption UXwindowsWindows-specific issues

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions