Skip to content

Avoid recursive stack exhaustion in SVN candidate traversal #1125

Description

@lzl51230

Related to #1113.

The SVN candidate walker recursively descends directories while retaining several path buffers per stack frame. A deeply nested working copy can exhaust the watcher thread stack even when the total path remains below platform limits.

Replace recursive traversal with a heap-backed worklist or otherwise bound stack usage. Add a deep-directory fixture that demonstrates traversal remains stable.

No activity

Activity on this issue will appear here.

Activity

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

    editor/integrationEditor compatibility and CLI integrationenhancementNew feature or requestpriority/normalStandard review queue; useful PR with ordinary maintainer urgency.stability/performanceServer crashes, OOM, hangs, high CPU/memorytaskUmbrella task grouping multiple related issuesux/behaviorDisplay bugs, docs, adoption UX

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions