Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(117)

Issue 11887011: Tighten up media::DecoderBuffer data requirements. (Closed)

Created:
7 years, 11 months ago by scherkus (not reviewing)
Modified:
7 years, 11 months ago
CC:
chromium-reviews, feature-media-reviews_chromium.org
Visibility:
Public.

Description

Tighten up media::DecoderBuffer data requirements. Calling DecoderBuffer::CopyFrom(NULL, 0) is a crashable offense as it's strong evidence that there's a bug in a demuxer generating NULL-containing packets. BUG=169133 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=177302

Patch Set 1 #

Patch Set 2 : Add test #

Patch Set 3 : #

Patch Set 4 : #

Total comments: 8

Patch Set 5 : #

Patch Set 6 : typo #

Unified diffs Side-by-side diffs Delta from patch set Stats (+48 lines, -20 lines) Patch
M media/base/decoder_buffer.h View 1 2 3 4 3 chunks +4 lines, -7 lines 0 comments Download
M media/base/decoder_buffer.cc View 1 2 3 4 5 2 chunks +13 lines, -13 lines 0 comments Download
M media/filters/ffmpeg_demuxer.cc View 1 1 chunk +20 lines, -0 lines 0 comments Download
M media/filters/ffmpeg_demuxer_unittest.cc View 1 2 3 4 1 chunk +11 lines, -0 lines 0 comments Download

Messages

Total messages: 3 (0 generated)
scherkus (not reviewing)
I'm not super happy w/ this CL but it at least makes us more strict ...
7 years, 11 months ago (2013-01-16 23:19:25 UTC) #1
acolwell GONE FROM CHROMIUM
LGTM % nits https://codereview.chromium.org/11887011/diff/8001/media/base/decoder_buffer.cc File media/base/decoder_buffer.cc (right): https://codereview.chromium.org/11887011/diff/8001/media/base/decoder_buffer.cc#newcode20 media/base/decoder_buffer.cc:20: buffer_size_ = 0; nit: CHECK_EQ(buffer_size, 0); ...
7 years, 11 months ago (2013-01-17 00:00:08 UTC) #2
scherkus (not reviewing)
7 years, 11 months ago (2013-01-17 00:16:30 UTC) #3
also renamed DecoderBuffer::buffer_size_ to DecoderBuffer::size_ (it was
confusing the heck out of me that we had data_ + buffer_size_)

https://codereview.chromium.org/11887011/diff/8001/media/base/decoder_buffer.cc
File media/base/decoder_buffer.cc (right):

https://codereview.chromium.org/11887011/diff/8001/media/base/decoder_buffer....
media/base/decoder_buffer.cc:20: buffer_size_ = 0;
On 2013/01/17 00:00:08, acolwell wrote:
> nit: CHECK_EQ(buffer_size, 0);

Done.

https://codereview.chromium.org/11887011/diff/8001/media/base/decoder_buffer....
media/base/decoder_buffer.cc:41: CHECK_GE(data_size, 0);
On 2013/01/17 00:00:08, acolwell wrote:
> nit: Perhaps move this one into the constructor?

Looks like a DCHECK equivalent is in Initialize() -- made that one a CHECK()
instead

https://codereview.chromium.org/11887011/diff/8001/media/filters/ffmpeg_demux...
File media/filters/ffmpeg_demuxer_unittest.cc (right):

https://codereview.chromium.org/11887011/diff/8001/media/filters/ffmpeg_demux...
media/filters/ffmpeg_demuxer_unittest.cc:622: // mistakently creating end of
stream buffers http://crbug.com/169133
On 2013/01/17 00:00:08, acolwell wrote:
> s/mistakently/mistakenly

Done.

https://codereview.chromium.org/11887011/diff/8001/media/filters/ffmpeg_demux...
media/filters/ffmpeg_demuxer_unittest.cc:624: #if
!defined(USE_PROPRIETARY_CODECS)
On 2013/01/17 00:00:08, acolwell wrote:
> nit: Why don't we just put all these tests in a single #if block or put the
> whole test inside an #if block? It doesn't seem like there is much value in
> having a empty test run in Chromium builds.

This way they still get compiled -- alternatively we can disable them w/ some
macro magic.

Powered by Google App Engine
This is Rietveld 408576698