media: Remove upper limit on number of frames in vpx decoder

    
In some extreme cases, we seem to be hitting the number of frames limit
on vpx video decoder. In those cases, there's a delay before chromium
releases the video frame. ffmpeg video decoder does not have any upper
limits on the number of video frames. So removing the limit on vpx video
decoder as well.

BUG=395431
TEST=media_unittests

Review URL: https://codereview.chromium.org/414523002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285184 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 0 insertions, 11 deletions

diff --git a/media/filters/vpx_video_decoder.cc b/media/filters/vpx_video_decoder.cc
index 9cadbca..ec902b8 100644
--- a/media/filters/vpx_video_decoder.cc
+++ b/media/filters/vpx_video_decoder.cc
@@ -71,13 +71,6 @@ static int GetThreadCount(const VideoDecoderConfig& config) {
   return decode_threads;
 }
 
-// Maximum number of frame buffers that can be used (by both chromium and libvpx
-// combined) for VP9 Decoding.
-// TODO(vigneshv): Investigate if this can be relaxed to a higher number.
-static const uint32 kVP9MaxFrameBuffers = VP9_MAXIMUM_REF_BUFFERS +
-                                          VPX_MAXIMUM_WORK_BUFFERS +
-                                          limits::kMaxVideoFrames;
-
 class VpxVideoDecoder::MemoryPool
     : public base::RefCountedThreadSafe<VpxVideoDecoder::MemoryPool> {
  public:
@@ -145,10 +138,6 @@ VpxVideoDecoder::MemoryPool::VP9FrameBuffer*
   }
 
   if (i == frame_buffers_.size()) {
-    // Maximum number of frame buffers reached.
-    if (i == kVP9MaxFrameBuffers)
-      return NULL;
-
     // Create a new frame buffer.
     frame_buffers_.push_back(new VP9FrameBuffer());
   }