-
Notifications
You must be signed in to change notification settings - Fork 325
fix: VRAM and memory leaks in window, session, output, and multi-GPU paths #2500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
minyek
wants to merge
11
commits into
pop-os:master
Choose a base branch
from
minyek:vram-leak-fixes
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
36f4961
fix(shell): free minimized-window GPU resources on client disconnect
minyek 2501172
fix(cursor): clear image cache on cursor shape change
minyek 3f07cf5
fix(activation): drop stale pending activations for dead Wayland surf…
minyek bd60e20
fix(session-lock): remove lock surfaces on output hot-unplug
minyek d663a32
fix(activation): drop stale X11 pending activations for unmapped windows
minyek e5fd690
fix(kms): free postprocess textures on GPU node removal
minyek 1ffd95c
fix(zoom): break Output→OutputZoomState→IcedElement reference cycle
minyek c35fd3d
fix(kms): remove disconnected client from all DRM devices
minyek f318021
chore: update smithay
minyek b92f55a
fix(kms): drain and invalidate the main-thread renderer caches
minyek 39aead4
fix(kms): join the surface thread when its connector is removed
minyek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of adding a new periodic cleanup function, should we be able to simply do a cleanup (or schedule a cleanup with
loop_handle.insert_idleafter output (re-)configuration?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think that'd fix the issue as the queue is populated at drop time, not import time — surfaces imported during (re-)configuration only become garbage later, when the window closes or the client exits. A cleanup right after configuration would run before that garbage exists and then never again, so e.g. a client exiting an hour after the last hotplug would stay pinned in VRAM until the next mode change. Since the resources are queued at arbitrary points (window close, client exit, cache eviction inside smithay), there's no single event that covers them all — hence the throttled drain (a make_current + empty try_iter at most every 2s).
We could make this event-based with a smithay change (e.g. a notifier/ping when a cleanup queue gets work), but for this PR I decided to keep the change contained to cosmic-comp.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right. I think ideally we would simply have a method on the
GraphicsApi/MultiRendererandGlesRendererto invalidate all caches. We know we don't need them and cleaning them up periodically still seems quite unnecessary to me.Would you consider making a smithay PR to add such methods?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I'm happy to make the smithay change and I agree it's a better solution. I'm away on holiday, so when I'm back next week I'll complete my testing and submit the smithay PR. Once that's approved, I'll update this PR.