fix: add memory safety caps and file watcher filtering (#259)#495
Merged
bradygaster merged 1 commit intodevfrom Mar 22, 2026
Merged
fix: add memory safety caps and file watcher filtering (#259)#495bradygaster merged 1 commit intodevfrom
bradygaster merged 1 commit intodevfrom
Conversation
Audit and mitigate resource-pressure patterns that could contribute to VS Code crashes during Squad execution (Issue #259, Discussion #174). Changes: - StreamingPipeline: cap usageData array at 1000 events (FIFO eviction) - TelemetryCollector: cap event queue at 500 events (FIFO eviction) - SquadObserver: filter orchestration-log/ and .git/ from fs.watch events - Add docs/reference/vscode-troubleshooting.md with root cause analysis, mitigations, and user-facing troubleshooting steps Closes #259 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
chrislomonico
pushed a commit
to clomonico/squad
that referenced
this pull request
Mar 26, 2026
Session: 2026-02-24T07-30-00Z-wave-d-batch1-impl Requested by: Coordinator Changes: - Logged orchestration for Cheritto (bradygaster#488, PR bradygaster#495): Unified Status Display - Logged orchestration for Fortier (bradygaster#493, PR bradygaster#494): StreamBuffer Cleanup on Error - Logged orchestration for Kovash (bradygaster#491, PR bradygaster#496): Message History Cap - Session log: Wave D batch 1 implementation summary - Decision inbox: empty (no new decisions to merge) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Investigates and mitigates resource-pressure patterns that could contribute to VS Code crashes during Squad execution.
Origin: Issue #259 (reported in Discussion #174 by @diberry)
Audit findings
Changes
Conclusion
The VS Code crash is most likely a VS Code Nightly renderer issue amplified by resource pressure from long-running Squad sessions. The fixes here reduce Squad memory and watcher footprint. The troubleshooting doc provides users with actionable mitigations.
Working as EECOM (Core Dev)
Closes #259