Fix possible buffer emission during an abort.

content/renderer/media/websourcebuffer_impl.cc

Index: content/renderer/media/websourcebuffer_impl.cc
diff --git a/content/renderer/media/websourcebuffer_impl.cc b/content/renderer/media/websourcebuffer_impl.cc
index ff3ac5b0079eaad191862c5bce60da8687bba712..2bb808e387fd589d53983c62857f244547cabc48 100644
--- a/content/renderer/media/websourcebuffer_impl.cc
+++ b/content/renderer/media/websourcebuffer_impl.cc
@@ -88,7 +88,7 @@ void WebSourceBufferImpl::append(
 }
 
 void WebSourceBufferImpl::abort() {
-  demuxer_->Abort(id_);
+  demuxer_->Abort(id_, timestamp_offset_);

[wolenetz, 2014/04/25 21:00:32]

append_window_{start,end}_ should also be part of processing any buffers the
parser emits as a result of abort() flushing the parser. For example, if an
emitted buffer is outside the append window, then it should not be buffered (and
a discontinuity should be triggered in case subsequent buffers fall within the
append window).
Also, |timestamp_offset_| might be updated by the coded frame processing
algorithm's processing of buffers emitted by the abort(). Pass it by reference
here?

[damienv1, 2014/05/05 22:39:13]

Done. Somehow, I was thinking that the timestamp offset was reset after an abort
(that's why I passed it by value).

 }
 
 void WebSourceBufferImpl::remove(double start, double end) {