Snapshot contention leaves lock artifacts and disk churn #15019

Activity

1. github-actions

   assigned

   thdxr

   on Feb 25, 2026
2. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   perfIndicates a performance issue or need for optimizationIndicates a performance issue or need for optimization

   on Feb 25, 2026
3. github-actions commented on Feb 25, 2026

   

   github-actionsBot

   on Feb 25, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue doesn't fully meet our contributing guidelines.

   What needs to be fixed:

   • No issue template was used. Please use one of the three required templates: Bug Report, Feature Request, or Question
   • If this is a bug report, it needs a description of steps to reproduce, your OS/environment, and OpenCode version
   • If this is a feature request, the title should start with [FEATURE]: and include a verification checkbox

   Please edit this issue to address the above within 2 hours, or it will be automatically closed.

   ---

   This issue might be a duplicate of existing issues. Please check:

   • Snapshot system leaks tmp_pack_* files indefinitely, filling disk at ~9.5 GB/hour #14811: Snapshot system leaks tmp_pack_* files indefinitely — same disk churn from snapshot operations
   • [ROOT CAUSE ANALYSIS] tmp_pack Leak - Complete Code Analysis & Fix Recommendations #10034: Root cause analysis of tmp_pack leak — covers lock contention, staging failures, and cleanup gaps
   • Snapshot.track() silently swallows git add failures, causing data loss on /undo #12719: Snapshot.track() silently swallows git add failures — directly related to staging/tree-write behavior under failure conditions

   If you believe this was flagged incorrectly, please let a maintainer know.
4. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Feb 25, 2026
5. github-actions commented on Feb 25, 2026

   

   github-actionsBot

   on Feb 25, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

   Feel free to open a new issue that follows our issue templates.
6. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Feb 25, 2026
7. github-actions

   closed this as not plannedon Feb 25, 2026