|
|
Chromium Code Reviews|
Created:
4 years, 1 month ago by liberato (no reviews please) Modified:
4 years, 1 month ago Reviewers:
DaleCurtis CC:
chromium-reviews, feature-media-reviews_chromium.org, posciak+watch_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionUse FFmpeg default padding when allocating audio buffers.
Previously, we would pad to the alignment size when allocating an
audio buffer. However, this did not always provide enough padding
to avoid overruns.
Instead, we now let FFmpeg determine the correct padding for us.
BUG=658440
Committed: https://crrev.com/b8733772baf52a693ab6a887373feaa6b91c7cdd
Cr-Commit-Position: refs/heads/master@{#429014}
Patch Set 1 #
Messages
Total messages: 16 (9 generated)
The CQ bit was checked by liberato@chromium.org to run a CQ dry run
Description was changed from ========== Use FFmpeg default padding when allocating audio buffers. Previously, we would pad to the alignment size when allocating an audio buffer. However, this did not always provide enough padding to avoid overruns. Instead, we now let FFmpeg determine the correct padding for us. BUG=658440 ========== to ========== Use FFmpeg default padding when allocating audio buffers. Previously, we would pad to the alignment size when allocating an audio buffer. However, this did not always provide enough padding to avoid overruns. Instead, we now let FFmpeg determine the correct padding for us. BUG=658440 ==========
liberato@chromium.org changed reviewers: + dalecurtis@chromium.org
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Can you add a ffmpeg_regression_test with this test case in it?
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Whoops thought I lgtm'd this to land as is. Test can be added separately
On 2016/11/01 16:05:44, DaleCurtis wrote: > Whoops thought I lgtm'd this to land as is. Test can be added separately cool, since the test is going badly :) first, it fails two test expectations. one is a bug in the test harness. OnDurationChanged is called twice, rather than the expected at most once, since the media duration isn't known in advance. there's also an expectation failure when seeking. the media time isn't being set properly to the seek point, and i'm trying to figure out why. oh, and the asan failure doesn't repro in the test anyway, since it needs to be run twice. not sure why yet -- certainly doesn't bode well for a good repro. adding two identical test cases does cause it, but not sure what's re-kershuffling the data around in memory yet.
The CQ bit was checked by liberato@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Use FFmpeg default padding when allocating audio buffers. Previously, we would pad to the alignment size when allocating an audio buffer. However, this did not always provide enough padding to avoid overruns. Instead, we now let FFmpeg determine the correct padding for us. BUG=658440 ========== to ========== Use FFmpeg default padding when allocating audio buffers. Previously, we would pad to the alignment size when allocating an audio buffer. However, this did not always provide enough padding to avoid overruns. Instead, we now let FFmpeg determine the correct padding for us. BUG=658440 ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== Use FFmpeg default padding when allocating audio buffers. Previously, we would pad to the alignment size when allocating an audio buffer. However, this did not always provide enough padding to avoid overruns. Instead, we now let FFmpeg determine the correct padding for us. BUG=658440 ========== to ========== Use FFmpeg default padding when allocating audio buffers. Previously, we would pad to the alignment size when allocating an audio buffer. However, this did not always provide enough padding to avoid overruns. Instead, we now let FFmpeg determine the correct padding for us. BUG=658440 Committed: https://crrev.com/b8733772baf52a693ab6a887373feaa6b91c7cdd Cr-Commit-Position: refs/heads/master@{#429014} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/b8733772baf52a693ab6a887373feaa6b91c7cdd Cr-Commit-Position: refs/heads/master@{#429014} |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
