diff options
| author | 2012-06-28 15:06:53 -0700 | |
|---|---|---|
| committer | 2012-06-28 17:08:42 -0700 | |
| commit | d58c304cc60be46a363fdcdce6da06e4ecb589b6 (patch) | |
| tree | 30ff2d25f110e5cc78ea12bb384eb0c0d7a04a9f /libs/gui/BufferQueue.cpp | |
| parent | f9783af225aa3b41ec0af36f90941a714269abb7 (diff) | |
Clarify aborted updateTexImage use of fences
When updateTexImage acquires a buffer but then aborts (due to an error
or the buffer being rejected), it releases the newly-acquired buffer.
It was passing the buffer slot's fences to releaseBuffer, even though
they hadn't been created after the acquire yet. This wasn't a bug,
since the fences would be cleared just after the buffer slot was last
released, but explicitly passing null fences makes this clearer.
Change-Id: I087f2ec3fd02c40f57782c1fca24eb9567e2943d
Diffstat (limited to 'libs/gui/BufferQueue.cpp')
0 files changed, 0 insertions, 0 deletions