fix: eliminate Athena resource spikes and freeze regressions - #190
Merged
Conversation
Owner
Author
|
Manual validation update: the resource-stability AppImage built from a497aa4 was tested by the user on the affected machine; they report that it looks good and works. This is additional smoke-test evidence. The two-hour multi-pane soak and Windows ConPTY hardware gate listed in the PR remain open. |
This was referenced Jul 20, 2026
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
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
Athena's freeze/heat problem is a combination of software-composited xterm painting, terminal delivery contracts that acknowledge before xterm drains, periodic whole-corpus session parsing, and agent fleets that can bypass memory admission.
The live Surface Laptop 3 profile that motivated this PR measured:
This PR fixes those causes as one resource/lifecycle contract and adds permanent tests for the regressions seen across #26, #57, #95-#100, #146, #154, #169-#172, #181, and #184.
What changed
Terminal delivery, visibility, and layout
Session discovery and allocation bounds
Launch admission, restore, and process lifecycle
MemAvailableonly.Adaptive Linux graphics
Regression protection and diagnostics
Why this avoids the previous regressions
Validation
git diff --check: passShort hardware canary on the affected Surface Laptop 3 (
Intel Iris Plus G7,8086:8a52, i915):This canary validates startup, mounted-xterm rendering, and clean fallback state on the known-risk device. It is not a substitute for the long soak below.
Known limits / follow-up gates
Checklist