[Mojo Video Capture] Retire buffers when Android Chromium goes to the background

media/capture/video/video_frame_receiver.h

Index: media/capture/video/video_frame_receiver.h
diff --git a/media/capture/video/video_frame_receiver.h b/media/capture/video/video_frame_receiver.h
index 55d98aa564ae49ca38a8761a9b788bd63810e621..0e269bc8dcee8ce1edcd75aa38dac4841a5f1fbc 100644
--- a/media/capture/video/video_frame_receiver.h
+++ b/media/capture/video/video_frame_receiver.h
@@ -21,7 +21,16 @@ class CAPTURE_EXPORT VideoFrameReceiver {
       scoped_refptr<media::VideoFrame> frame) = 0;
   virtual void OnError() = 0;
   virtual void OnLog(const std::string& message) = 0;
-  virtual void OnBufferDestroyed(int buffer_id_to_drop) = 0;
+
+  // Tells the VideoFrameReceiver that the producer is no longer going to use
+  // the buffer with id |buffer_id| for frame delivery. This may be called even
+  // while the receiver is still consuming the buffer from a call to
+  // OnIncomingCapturedVideoFrame(). In that case, it means that the
+  // caller is asking the VideoFrameReceiver to release the buffer
+  // at its earliest convenience.

[miu, 2017/01/31 01:18:51]

nit: Does "at its earliest convenience" really mean "once there are no consumers
referencing the frame?"

[chfremer, 2017/01/31 18:54:28]

In case of the concrete implementation VideoCaptureController this is indeed how
we do it. 

However, this information belongs with the concrete class VideoCaptureController
and not with this interface VideoFrameReceiver. That is the reason why I
formulated it in such loose terms. The code operating the VideoFrameReceiver
should not need to know what the implementation is, and it should not care how
long that implementation holds on to retired buffers.

+  // The producer guarantees that it does not reuse a retired |buffer_id| before
+  // having cycled through all other possible values.
+  virtual void OnBufferRetired(int buffer_id) = 0;
 };
 
 }  // namespace media