Skip to content
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

Buffers are not always recycled automatically #111

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

b100dian
Copy link

@b100dian b100dian commented Jul 18, 2023

This was observed on asus sake, media buffers on, a lineage-18.1 port which uses media buffers: the mGraphicBuffer was not recycled (did not come null). The previous one from the slot needed to be unref'd.

The pointer itself is not, since clients are not aware of this change.

So a pointer tracking was introduced that allows clients to have DroidMediaBuffer pointers even if they are devoid of resources until the releaseBuffers call comes in which also clears the memory.

Change-Id: Ifc1b59535c34c12a1db11808b0ae6c59337dee20
@b100dian b100dian marked this pull request as draft July 18, 2023 23:08
@b100dian b100dian marked this pull request as ready for review July 20, 2023 19:31
private.cpp Outdated Show resolved Hide resolved
private.h Show resolved Hide resolved
Change-Id: I323b20177b4298cf5848266e84bf9d73d9084c6f
Change-Id: I4c576c5d1b44b014a69aa0ab131491cd52e5c678
Change-Id: I8492f91eca7c8709faae42a2f1be69108c932a3a
Change-Id: Ia25af46b92b6b53a6fa0d262bf89cd10e73add94
Change-Id: Ife94eb380e2d9488a1dfdec1a2526d926e284c3e
Change-Id: I7b5f6c1b2f142ef46a9cf73c3ccaa33e691b306f
Change-Id: I594c5cecfbf582e15cb20a7e79230897d4882f12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants