Add performance tracing event to VideoCaptureDeviceAndroid::OnFrameAvailable

BUG=329505

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245531 0039d316-1c4b-4281-b951-d872f2087c98
Blink roll 165308:165310

http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=165309:165310&mode=html
TBR=
BUG=

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245532 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 245532
Quota: Factor out (Mock)QuotaManagerProxy into its own file for readability


BUG=n/a
TEST=compile (mechanical changes only)
TBR=michaeln@chromium.orgjochen@chromium.org

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

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245534 0039d316-1c4b-4281-b951-d872f2087c98
Make sure to initialize a boolean in ExtensionSettingsHandler

It turns out there are 2 constructors, and this boolean was only being
initialized to false in one of them. This caused an extension install
verification request to the verification server on every load of the
chrome://extensions page (regardless of whether the user had any
disabled-due-to-verification-failure extensions).

Also add a histogram for tracking the number of ids that we tried to 
verify which the server replied were invalid (ie not known to be in the
webstore). 


BUG=335379

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

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@245535 0039d316-1c4b-4281-b951-d872f2087c98
SVN changes up to revision 245534
SVN changes up to revision 245535