Log stream parsing errors in ChunkDemuxer

media/filters/chunk_demuxer.cc

Index: media/filters/chunk_demuxer.cc
diff --git a/media/filters/chunk_demuxer.cc b/media/filters/chunk_demuxer.cc
index 505d9c1f69c6a8275ad437ce23bd7374b72ffb97..55ff88c2dac11361fa76d67e999024465d14cdae 100644
--- a/media/filters/chunk_demuxer.cc
+++ b/media/filters/chunk_demuxer.cc
@@ -330,10 +330,17 @@ bool SourceState::Append(
 
   // TODO(wolenetz/acolwell): Curry and pass a NewBuffersCB here bound with
   // append window and timestamp offset pointer. See http://crbug.com/351454.
-  bool err = stream_parser_->Parse(data, length);
+  bool result = stream_parser_->Parse(data, length);
+  if (!result) {
+    MEDIA_LOG(log_cb_)
+        << __FUNCTION__ << ": stream parsing failed."

[wolenetz, 2014/10/07 22:50:48]

How does it look in chrome://media-internals when such a failure occurs? Is
inclusion of __FUNCTION__ too much detail?

+        << " Data size=" << length
+        << " append_window_start=" << append_window_start.InSecondsF()
+        << " append_window_end=" << append_window_end.InSecondsF();
+  }
   timestamp_offset_during_append_ = NULL;
   init_segment_received_cb_.Reset();
-  return err;
+  return result;
 }
 
 void SourceState::Abort(TimeDelta append_window_start,