Don't crash on splice frame failure with bad content.

Don't crash on splice frame failure with bad content.

Turns out this isn't something we can CHECK() if the content has
"bad" timestamps. "bad" in this case being either a bad file or
a bug in the timestamping code.  I haven't figured out which yet,
but in either case we shouldn't crash.

BUG=388068
TEST=new unittest

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=279817

[DaleCurtis, 2014-06-24 01:57:49]

Crashing is just no fun.

[acolwell GONE FROM CHROMIUM, 2014-06-25 16:27:55]

lgtm

https://codereview.chromium.org/339433006/diff/20001/media/base/audio_splicer...
File media/base/audio_splicer_unittest.cc (right):

https://codereview.chromium.org/339433006/diff/20001/media/base/audio_splicer...
media/base/audio_splicer_unittest.cc:686: // between whats in the pre splice and
post splice that is too large to recover
nit: s/whats/what's/

[DaleCurtis, 2014-06-25 18:30:10]

Thanks for review!

https://codereview.chromium.org/339433006/diff/20001/media/base/audio_splicer...
File media/base/audio_splicer_unittest.cc (right):

https://codereview.chromium.org/339433006/diff/20001/media/base/audio_splicer...
media/base/audio_splicer_unittest.cc:686: // between whats in the pre splice and
post splice that is too large to recover
On 2014/06/25 16:27:55, acolwell wrote:
> nit: s/whats/what's/

Done.

[DaleCurtis, 2014-06-25 18:30:13]

The CQ bit was checked by dalecurtis@chromium.org

[commit-bot: I haz the power, 2014-06-25 18:33:45]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/dalecurtis@chromium.org/339433006/40001

[commit-bot: I haz the power, 2014-06-25 21:15:12]

Change committed as 279817