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

Android: Faking releaseBufferCallback from transactionCompleteCallback #13737

Open
1 task done
m1ga opened this issue Jan 31, 2023 · 0 comments
Open
1 task done

Android: Faking releaseBufferCallback from transactionCompleteCallback #13737

m1ga opened this issue Jan 31, 2023 · 0 comments
Labels

Comments

@m1ga
Copy link
Contributor

m1ga commented Jan 31, 2023

I have searched and made sure there are no existing issues for the issue I am filing

  • I have searched the existing issues

Description

Just an info for people having the same - nothing we can fix at the moment:

On my Pixel 7 I receive those logs for some time now:

E/BLASTBufferQueue: [VRI[TiActivity]#4](f:0,a:2) Faking releaseBufferCallback from transactionCompleteCallback

Here is a good summary of the problem: https://stackoverflow.com/a/75041612/5193915
It started with the December Android 13 patch update.
Summery:

Finally, to summarize this log can be safely ignored.

Its annoying and I hope they'll remove it again (like the map exceeded sample count in FrameTime log). In the meantime: use cli.ignoreLog in ti config to exclude it from showing up in the logs.

Platform

Android

SDK version you are using

12.1.0

@m1ga m1ga added bug needs triage This issue hasn't been reviewed by maintainers and removed needs triage This issue hasn't been reviewed by maintainers labels Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant