Use -1 consistently as invalid buffer idx
Instead of mixed use of both -1 and INT_MAX. This also fixes a vp9 fuzzing test failure. Change-Id: I950ea94b44ec7cdb5232773bee30b104e342f52a
This commit is contained in:
parent
0979dbb37b
commit
61c5e94e22
@ -238,7 +238,7 @@ static void swap_frame_buffers(VP9Decoder *pbi) {
|
||||
|
||||
// Invalidate these references until the next frame starts.
|
||||
for (ref_index = 0; ref_index < 3; ref_index++)
|
||||
cm->frame_refs[ref_index].idx = INT_MAX;
|
||||
cm->frame_refs[ref_index].idx = -1;
|
||||
}
|
||||
|
||||
int vp9_receive_compressed_data(VP9Decoder *pbi,
|
||||
@ -258,7 +258,7 @@ int vp9_receive_compressed_data(VP9Decoder *pbi,
|
||||
// TODO(jkoleszar): Error concealment is undefined and non-normative
|
||||
// at this point, but if it becomes so, [0] may not always be the correct
|
||||
// thing to do here.
|
||||
if (cm->frame_refs[0].idx != INT_MAX)
|
||||
if (cm->frame_refs[0].idx > 0)
|
||||
cm->frame_refs[0].buf->corrupted = 1;
|
||||
}
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user