Fixing crash in buffer bar painting code
commitbab6495e6a0493e7419b07108d9b8cada17853d6
authorvrk@google.com <vrk@google.com@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 28 Jul 2010 22:54:55 +0000 (28 22:54 +0000)
committervrk@google.com <vrk@google.com@0039d316-1c4b-4281-b951-d872f2087c98>
Wed, 28 Jul 2010 22:54:55 +0000 (28 22:54 +0000)
tree8ed34af0dbe36febf6d6900b6157ce1f51f0abdf
parent702d256f98fc70f835d0d23cf093d08eadbeaf9e
Fixing crash in buffer bar painting code

Crash was because of inconsistent state caused by threading issues.
The state of the buffer bar isn't so critical to need to be 100% accurate
at all times, so this is fixed by capping the buffered_bytes_ and
current_bytes to always be at legal values.

BUG=49870
TEST=media_unittests
TBR=hclam

Review URL: http://codereview.chromium.org/3045021

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@54055 0039d316-1c4b-4281-b951-d872f2087c98
media/base/pipeline_impl.cc