comma: release GBM scanout buffers on close#29
Open
adeebshihadeh wants to merge 1 commit intomasterfrom
Open
Conversation
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.
Fixes a COMMA platform teardown leak where UI process exits leave mdss-backed dma-bufs pinned. The close path now releases the active GBM BO, destroys the GBM surface before destroying the device, closes the DRM fd, and clears tracked BO/FB state after swaps.
Validated on tizi with a UI-only pyray probe: the mdss 9400320-byte dma-buf count stays flat across repeated gui_app.close() cycles with this patch; the old build leaked three such buffers per UI process restart.