Fix handling non-tightly packed ByteBuffers in HardwareVideoDecoder.
Before this CL, there would be an out-of-bounds write in the ByteBuffer copying when a decoded frame had height != sliceHeight. Bug: webrtc:9194 Change-Id: Ibb80e5555e8f00d9e1fd4cb8a73f5e4ccd5a0b81 Tested: 640x360 loopback with eglContext == null in AppRTCMobile on Pixel. Reviewed-on: https://webrtc-review.googlesource.com/74120 Commit-Queue: Sami Kalliomäki <sakal@webrtc.org> Reviewed-by: Rasmus Brandt <brandtr@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23184}
This commit is contained in:
committed by
Commit Bot
parent
c710ac142e
commit
ee98be7811
@ -114,8 +114,8 @@ TEST(VideoProcessorIntegrationTestMediaCodec,
|
||||
TEST(VideoProcessorIntegrationTestMediaCodec, ForemanMixedRes100kbpsVp8H264) {
|
||||
auto config = CreateTestConfig();
|
||||
const int kNumFrames = 30;
|
||||
// TODO(brandtr): Add H.264 when we have fixed the encoder.
|
||||
const std::vector<std::string> codecs = {cricket::kVp8CodecName};
|
||||
const std::vector<std::string> codecs = {cricket::kVp8CodecName,
|
||||
cricket::kH264CodecName};
|
||||
const std::vector<std::tuple<int, int>> resolutions = {
|
||||
{128, 96}, {160, 120}, {176, 144}, {240, 136}, {320, 240}, {480, 272}};
|
||||
const std::vector<RateProfile> rate_profiles = {
|
||||
|
||||
Reference in New Issue
Block a user