-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Avoid recursive stack exhaustion in SVN candidate traversal #1125
Copy link
Copy link
Open
Labels
editor/integrationEditor compatibility and CLI integrationEditor compatibility and CLI integrationenhancementNew feature or requestNew feature or requestpriority/normalStandard review queue; useful PR with ordinary maintainer urgency.Standard review queue; useful PR with ordinary maintainer urgency.stability/performanceServer crashes, OOM, hangs, high CPU/memoryServer crashes, OOM, hangs, high CPU/memorytaskUmbrella task grouping multiple related issuesUmbrella task grouping multiple related issuesux/behaviorDisplay bugs, docs, adoption UXDisplay bugs, docs, adoption UX
Milestone
Description
Metadata
Metadata
Assignees
Labels
editor/integrationEditor compatibility and CLI integrationEditor compatibility and CLI integrationenhancementNew feature or requestNew feature or requestpriority/normalStandard review queue; useful PR with ordinary maintainer urgency.Standard review queue; useful PR with ordinary maintainer urgency.stability/performanceServer crashes, OOM, hangs, high CPU/memoryServer crashes, OOM, hangs, high CPU/memorytaskUmbrella task grouping multiple related issuesUmbrella task grouping multiple related issuesux/behaviorDisplay bugs, docs, adoption UXDisplay bugs, docs, adoption UX
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.