diff options
| author | 2021-10-14 11:57:22 -0500 | |
|---|---|---|
| committer | 2021-10-14 12:02:38 -0500 | |
| commit | 6ebdf5f0f7ca5354a1a9a0e6419275c7b873849d (patch) | |
| tree | acab044a905803769f32eacff618510219bec9e6 /libs/gui/BLASTBufferQueue.cpp | |
| parent | 3ef0b97f2805a13f32051b87c5d723300b38bf66 (diff) | |
Use bufferItem's fence when calling release
When we acquire and release immediately, we want to use the bufferItem's
release fence instead of NO_FENCE.
Also add an error log if there's a failure in acquireBuffer, which
really should never happen.
Test: BLASTBufferQueueTest
Bug: 200285149
Change-Id: I5e869b0f66f37b15b9317985b30f539dbfea831c
Diffstat (limited to 'libs/gui/BLASTBufferQueue.cpp')
| -rw-r--r-- | libs/gui/BLASTBufferQueue.cpp | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/libs/gui/BLASTBufferQueue.cpp b/libs/gui/BLASTBufferQueue.cpp index 2d2b6b26f6..dfbb8630c0 100644 --- a/libs/gui/BLASTBufferQueue.cpp +++ b/libs/gui/BLASTBufferQueue.cpp @@ -597,9 +597,15 @@ Rect BLASTBufferQueue::computeCrop(const BufferItem& item) { void BLASTBufferQueue::acquireAndReleaseBuffer() { BufferItem bufferItem; - mBufferItemConsumer->acquireBuffer(&bufferItem, 0 /* expectedPresent */, false); - mBufferItemConsumer->releaseBuffer(bufferItem, Fence::NO_FENCE); + status_t status = + mBufferItemConsumer->acquireBuffer(&bufferItem, 0 /* expectedPresent */, false); + if (status != OK) { + BQA_LOGE("Failed to acquire a buffer in acquireAndReleaseBuffer, err=%s", + statusToString(status).c_str()); + return; + } mNumFrameAvailable--; + mBufferItemConsumer->releaseBuffer(bufferItem, bufferItem.mFence); } void BLASTBufferQueue::onFrameAvailable(const BufferItem& item) { |