fix an out-of-bounds memory access
in this particular case, this OOB is always harmless (and that's why it didn't get fixed from MR1), however, it interfers with valgrind debugging. Change-Id: Ic977e03287e59c4b124a89146c9023bd0cb540a8
This commit is contained in:
parent
ee932d0ad1
commit
2a8c49eb5d
@ -314,13 +314,15 @@ status_t BufferQueue::dequeueBuffer(int *outBuf, sp<Fence>& outFence,
|
||||
* the consumer may still have pending reads of the
|
||||
* buffers in flight.
|
||||
*/
|
||||
if (found >= 0) {
|
||||
bool isOlder = mSlots[i].mFrameNumber <
|
||||
mSlots[found].mFrameNumber;
|
||||
if (found < 0 || isOlder) {
|
||||
if (isOlder) {
|
||||
found = i;
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
// clients are not allowed to dequeue more than one buffer
|
||||
// if they didn't set a buffer count.
|
||||
|
Loading…
Reference in New Issue
Block a user