VP9 temporal index bounds check.
Bug: chromium:838672 Change-Id: Ia531327858b6e40cb7fa03ca1b98c120ba4e1389 Reviewed-on: https://webrtc-review.googlesource.com/73701 Reviewed-by: Stefan Holmer <stefan@webrtc.org> Commit-Queue: Philip Eliasson <philipel@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23099}
This commit is contained in:
@ -533,6 +533,12 @@ bool RtpFrameReferenceFinder::MissingRequiredFrameVp9(uint16_t picture_id,
|
||||
size_t gof_idx = diff % info.gof->num_frames_in_gof;
|
||||
size_t temporal_idx = info.gof->temporal_idx[gof_idx];
|
||||
|
||||
if (temporal_idx >= kMaxTemporalLayers) {
|
||||
RTC_LOG(LS_WARNING) << "At most " << kMaxTemporalLayers << " temporal "
|
||||
<< "layers are supported.";
|
||||
return true;
|
||||
}
|
||||
|
||||
// For every reference this frame has, check if there is a frame missing in
|
||||
// the interval (|ref_pid|, |picture_id|) in any of the lower temporal
|
||||
// layers. If so, we are missing a required frame.
|
||||
|
||||
Reference in New Issue
Block a user