GitLab

This CL migrates ArcAudioBridge.

BUG=672829
TEST=Ran try.

Change-Id: I2d48c86e0ba20bc98d28b09e25a309b888304610
Reviewed-on: https://chromium-review.googlesource.com/571344Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Commit-Queue: Hidehiko Abe <hidehiko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486972}

https://boringssl.googlesource.com/boringssl/+log/52586f952ecb624f823eb9ee5ef2eb41e644e7f5..14308731e5446a73ac2258688a9688b524483cb6

This picks up, among other things, the fix to some ServerHello parsing.

Bug: 743218
Change-Id: I45316af58f675f59ae141f9f1379690010bf04c7
Reviewed-on: https://chromium-review.googlesource.com/572621Reviewed-by: Adam Langley <agl@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486971}

https://skia.googlesource.com/skia.git/+log/f2c901474c24..1a325d25b941

$ git log f2c901474..1a325d25b --date=short --no-merges --format='%ad %ae %s'
2017-07-14 csmartdalton Coverage counting path renderer
2017-07-14 scroggo Report error on failure to create SkCodec
2017-07-14 ethannicholas converted GrBlurredEdgeFragmentProcessor to sksl
2017-07-14 csmartdalton Fix SkClassifyCubic for near-quadratics
2017-07-14 brianosman Revert "remove dead code for legacy image encode api"
2017-07-14 bsalomon Make GrAtlasTextOp a non-legacy GrMeshDrawOp
2017-07-14 ethannicholas converted EllipseEffect to sksl

Created with:
  roll-dep src/third_party/skia


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=ethannicholas@chromium.org

Change-Id: Iee5257b138cec85ae8f0e71a5285028771b6ddad
Reviewed-on: https://chromium-review.googlesource.com/572563Reviewed-by: Skia Deps Roller <skia-deps-roller@chromium.org>
Commit-Queue: Skia Deps Roller <skia-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486970}

The spec[1] was changed.

[1] https://github.com/w3c/payment-handler/pull/167

Bug: 661608
Change-Id: I38e7ff1d6e6da4ffb99e83fdb37f4cda94eab91d
Reviewed-on: https://chromium-review.googlesource.com/565078Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Jinho Bang <jinho.bang@samsung.com>
Cr-Commit-Position: refs/heads/master@{#486969}

BUG=730889
R=sadrul@chromium.org

Change-Id: I4b28a1e0a70236e2410eed9d442481db5fb0c898
Reviewed-on: https://chromium-review.googlesource.com/572054Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486968}

This change switches the VS 2017 package to use the 10.0.15063.468 SDK
and the fourth preview of VS 2017 Update 3.

Packaging was done on a Windows Server 2016 VM, cleanly created for this
purpose.

Compiler was packaged up by downloading the VS 2017 Update 3 Preview 4,
from https://www.visualstudio.com/vs/preview/, and then running this
command (executable name was different):

    vs_professional.exe --add Microsoft.VisualStudio.Workload.NativeDesktop
    --add Microsoft.VisualStudio.Component.VC.ATLMFC --includeRecommended
    --passive

Then the Windows 10.0.15063.468 SDK installer was used to install the
Debuggers package.

The latest version of vswhere.exe doesn't show pre-release versions of
VS by default so win_toolchain/package_from_installed.py was locally
patched to add the -prerelease flag to the vswhere.exe invocation.

Then the packaging script was run like this:

    python depot_tools\win_toolchain\package_from_installed.py 2017 -w 10.0.15063.0

VS 2015 builds are still the default so this makes no immediate difference.

R=dpranke@chromium.org
BUG=683729

Change-Id: Ic9515f6f315931c72a762411ea6713e86351ce37
Reviewed-on: https://chromium-review.googlesource.com/572480
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486967}

Prior to launching Safe Mode, we want to verify that there won't be a
significant number of false positives, which might otherwise cause more harm
than good. This CL adds metrics to measure how often Safe Mode would trigger,
without actually enabling safe mode even when the heuristics say it should
trigger.

R=asvitkine@chromium.org

Bug: 727984
Change-Id: I83b909bf81ec8c6416f47151c17fe4e53725ee3c
Reviewed-on: https://chromium-review.googlesource.com/570731
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Alexei Svitkine (slow) <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486966}

Make two changes to how we initialize features for contexts in extension
native bindings:
- Treat runtime specially. This is necessary because certain runtime
  methods should be exposed only if there exists an extension that can
  connect to the given context (e.g., an extension that cooperates with
  a given website).  Simply checking the fature availability is
  insufficient. Update unittests to match.
- Treat web contexts specially.  Web contexts only ever have a handful
  (3) APIs that are potentially available to them, and are by far the
  most commonly created context. As such, add a fast path for them by
  only checking those possible features. (This matches logic in the
  JS bindings system).

Bug: 653596
Change-Id: I57f50b6f762f578679771c5e07a1b3ce31da3e0c
Reviewed-on: https://chromium-review.googlesource.com/571962Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486965}

Added --disable-all-origin-trial-controlled-features which will turn off
all RuntimeEnabledFeatures that can be enabled by OT. These features can
then only be enabled with a valid trial token.

Bug: 685788
Change-Id: Ic5e3976fe51482794107ca82c32412f2b47aee8c
Reviewed-on: https://chromium-review.googlesource.com/568807
Commit-Queue: Alex Vallee <avallee@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Jason Chase <chasej@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486964}

When running GPU thread inside browser process, GpuPreferences is not
updated from GPU command line switches and blacklists. So we need update
those preferences in GpuDataManagerImplPrivate::UpdateGpuPreferences
when in_process_ is true.

Change-Id: Ic60e778e0c436b8f44365eec70c2855935629a54
Reviewed-on: https://chromium-review.googlesource.com/569324Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486963}

If we always build clang with symbols on Windows then it makes debugging
and profiling easier. The build time costs shouldn't be too bad, and the
generated code will be identical. This would have saved a bit of time in
the investigation of crbug.com/727447.

BUG=727447

Change-Id: Ib065be626db5d6b0b9c27792a0141c5fb696e208
Reviewed-on: https://chromium-review.googlesource.com/572660Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486962}

This reverts commit 4f552ac6.

Reason for revert: Caused unit test failures, see https://crbug.com/743211

Original change's description:
> shelf: Add a back button to the shelf.
> 
> This is in preparation for removing title bars work. See mocks in the bug and screenshots for more details. 
> This approach of adding a back button expands the current app list button to be modal and have two functionalities
> depending on which side is pressed. The alternative (seperate back button) is IMO very difficult to achieve what
> is shown in the mocks (namely the color in between and animation (not in this CL) of said color in between). The
> exact functionality of the back button is not 100% defined yet, this CL just sends a VKEY_BROWSER_BACK event in the
> meantime.
> 
> Screenshots:
> https://screenshot.googleplex.com/ZVNP0aq0cc3
> https://screenshot.googleplex.com/fDcGTuoyZg5
> https://screenshot.googleplex.com/ZFBzk72LLVt
> 
> Test: ash_unittests --gtest_filter="ShelfViewInkDropTest.*"
> Bug: 721940
> Change-Id: I699c6d971aea89ba201536ca8534a14b4d44b0e2
> Reviewed-on: https://chromium-review.googlesource.com/555836
> Commit-Queue: Sammie Quon <sammiequon@chromium.org>
> Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
> Reviewed-by: Michael Wasserman <msw@chromium.org>
> Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#486830}

TBR=msw@chromium.org,oshima@chromium.org,xdai@chromium.org,sammiequon@chromium.org,msw@google.com

Change-Id: Id4eb870a99514a7f2b64cbe35d993047d0cc43e4
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 721940
Reviewed-on: https://chromium-review.googlesource.com/572682Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486961}

This CL moves the policy indicator on the homepage url from under the
input to the same line as the input.

Bug: 736149
Change-Id: I3896b3e77284a82742ae51ea1d6fe86753087488
Reviewed-on: https://chromium-review.googlesource.com/570821Reviewed-by: Scott Chen <scottchen@chromium.org>
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486960}

This implements the user image picker to look and behave the same
as the Settings UI.

Notes:
* Because we use the same icon and camera size, the icons overflow
  and scroll. This is consistent with the new UX so seems acceptable
  as an intermediate step.
* The supervised user picker has not been changed yet, pending the
  status of the feature.

Bug: 730031
Change-Id: Iaa1044e5eb57f37677d52ba592a7fcb470803abe
Reviewed-on: https://chromium-review.googlesource.com/569311
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486959}

Some units have a dedicated "hamburger" key. Let's use it as an
accelerator to invoke the system tray.

BUG=b:63576567

Change-Id: Iead7b38daae9da0c4f14362e14e13e9ee9345c8c
Reviewed-on: https://chromium-review.googlesource.com/571610Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Dmitry Torokhov <dtor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486958}

Previously FFmpegDemuxer would release all unnecessary audio/video
streams. But with multi-track support unused a/v streams are disabled
instead of being released. So now we need to exclude disabled streams
in FFmpegDemuxer::StreamsHaveAvailableCapacity, otherwise it will
always return true (since disabled streams always have available
capacity), causing FFmpegDemuxer memory usage to grow unbounded.

BUG=740138

Change-Id: I4f2c990232a01988f66ff475bbb8b9970aff742f
Reviewed-on: https://chromium-review.googlesource.com/572231
Commit-Queue: Sergey Volk <servolk@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486957}

Rather than using the fixed kTopPadding. This ensures the UI is mostly
centered in screen size and orientation.

Change-Id: Ia78f020a84566873ceb08f837917b5bf722ab4af
Reviewed-on: https://chromium-review.googlesource.com/571682Reviewed-by: Scott Nichols <nicholss@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486956}

BUG=715263
R=afakhry@chromium.org, tbarzic@chromium.org

Change-Id: I81de5e5f0e2e6940ea97fe771c9c7b4c86058f36
Reviewed-on: https://chromium-review.googlesource.com/571328
Commit-Queue: Simon Que <sque@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486955}

BUG=719580
TBR=zmo@chromium.org
NOTRY=true

Change-Id: I269323e598a55e055d32a3b7055d4342b2150b7b
Reviewed-on: https://chromium-review.googlesource.com/572681
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486954}

This patch adds ShapeResult and line orientation to
NGPhysicalTextFragment. These properties are not used today, but will be
used in LayoutNGPaintFragments.

Includes cleanup of functions that are no longer used.

BUG=636993
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_layout_ng

Change-Id: Id91f177e8d9d91914144ab138f37f25cd612be2f
Reviewed-on: https://chromium-review.googlesource.com/571883Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486953}

Bug: 
Change-Id: Iffc70523b255f49ac905dc0db51b0f9ef758669f
Reviewed-on: https://chromium-review.googlesource.com/572221
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Jialiu Lin <jialiul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486952}

BUG=706512

Change-Id: I185278d5230b00dc6b8b9c3a8712ae016b7d44f3
Reviewed-on: https://chromium-review.googlesource.com/572190
Commit-Queue: Gabriel Charette <gab@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486951}

BUG=706512

Change-Id: I933e2b06530b9d164a33966e9b70125729fc80ff
Reviewed-on: https://chromium-review.googlesource.com/572404Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486950}

BrowserCommandController interactive test ensures the recent changes of browser
shortcuts in fullscreen won't be broken by unexpected changes. It starts a full
screen browser window, sends several key events normally consumed by browser,
and checks whether these events are caught by the web page.

BUG=680809

Review-Url: https://codereview.chromium.org/2922773002
Cr-Commit-Position: refs/heads/master@{#486949}

Currently volume change requests are sent only when the user clicks and releases
the click. This CL makes it send requests even while the user is dragging the
slider knob, to match the behavior of the extensionview controller.

Bug: 742419
Change-Id: I17e7d53fcf801e1cf720de4789f7b36aaf6dd6f8
Reviewed-on: https://chromium-review.googlesource.com/562836
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486948}

Currently when mojo CDM is enabled it is hosted in the MediaService
running in the process specified by "mojo_media_host". However, on
some platforms we need to run mojo CDM and other mojo media services in
different processes. For example, on desktop platforms, we want to run
mojo video decoder in the GPU process, but run the mojo CDM in the
utility process.

This CL adds a new build flag "enable_standalone_cdm_service". When
enabled, the mojo CDM service will be hosted in a standalone "cdm"
service running in the utility process. All other mojo media services
will sill be hosted in the "media" servie running in the process
specified by "mojo_media_host".

BUG=664364
TEST=Encrypted media browser tests using mojo CDM is still working.

Change-Id: I95be6e05adc9ebcff966b26958ef1d7becdfb487
Reviewed-on: https://chromium-review.googlesource.com/567172
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486947}

This is a reland of 0ac8d89e
Original change's description:
> Fix thread safety issues with safe browsing DB.
> 
> Fix thread safety issues with safe browsing DB.
> The Safe Browsing DB has some sequence consistency issues, which
> is caught by the stricter WeakPtr semantics detailed on CL 2908073007.
> 
> * Delete SafeBrowsingDatabaseManager on IO thread.
> * Remove illegal dereferencing of IO-thread WeakPtr from DB thread in
>   V4Database::VerifyChecksumOnTaskRunner
> * Remove non-threadsafe accesses of |io_thread_| resident members from
>   the DB thread in V4LocalDatabaseManager.
> * Add IO-thread runloops to unit tests to handle database teardown.
> 
> 
> R=nparker@chromium.org
> CC=wez@chromium.org
> 
> Bug: 729716
> Change-Id: I1bc620d42aca2f1cc99e482b7776a628d783d390
> Reviewed-on: https://chromium-review.googlesource.com/523983
> Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
> Reviewed-by: Charlie Harrison <csharrison@chromium.org>
> Reviewed-by: Greg Thompson <grt@chromium.org>
> Reviewed-by: Varun Khaneja <vakh@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#481735}

TBR=csharrison@chromium.org, grt@chromium.org, vakh@chromium.org

Bug: 729716, 742596
Change-Id: I4d67aa201c54be7a1e75a7375ac9861a29f1d87f
Reviewed-on: https://chromium-review.googlesource.com/571684Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486946}

This CL changes some old content Polymer slotting with the newer keyword
slot. These are the simple, unnamed cases in MD settings. The cases that
use slot names will be done separately.

Bug: 739532
Change-Id: I7a4bd4c186f1e4e576bb19569bdd45a9264a1ff0
Reviewed-on: https://chromium-review.googlesource.com/564062Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Dave Schuyler <dschuyler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486945}

Previously, we omitted these clips, as an inadvertent side-effect
of avoiding clipping to the dirty rect.

Bug: 734116
Change-Id: I6dcd92b80b8158f36689d5b48d92a0bdf43bb016
Reviewed-on: https://chromium-review.googlesource.com/567520
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486944}

The blocking pool has been deprecated in favor of TaskScheduler.

Bug: 667892
Change-Id: Iabaa23abc14ade5b5c0e4ed9bee6b8f574d7b689
Reviewed-on: https://chromium-review.googlesource.com/571306Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486943}

Up until now, each in-product help feature has recorded their own
histogram for how often they are triggered. However, this makes it
hard to inspect the overall data for how often in-product help is
triggered in general.

This CL therefore adds a new histogram that is triggered regardless of
which feature invoked it: InProductHelp.ShouldTriggerHelpUI. That name
is also the base name for the suffix-based feature specific histograms.

In addition, tests are added to ensure these histograms behave as
expected.

BUG=733799

Change-Id: I9c99494dc64f9c20fc2e811d7596ff0d7a7f72c2
Reviewed-on: https://chromium-review.googlesource.com/569259
Commit-Queue: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Alexei Svitkine (slow) <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486942}

This CL moves PrimaryBeginFrameSource to components/viz/service/frame_sinks
and updates all the appropriate includes, forward declarations, and
namespaces.

Bug: 722935
Change-Id: I8f7021a1cc1b262c1ebc18ee5ff1287eb91772ef
Reviewed-on: https://chromium-review.googlesource.com/571268
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486941}

Bug: 741969
Change-Id: Id80b178aee043babd25a533e21fc25118a446d77
Reviewed-on: https://chromium-review.googlesource.com/572424Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486940}

We have collected adequate data from
Cookie.CookieLineCookieValueValidity. Remove it.

BUG=638117

Change-Id: Iab9d2b095cebda9a4b1cf0fdb572aa6ee30a457d
Reviewed-on: https://chromium-review.googlesource.com/571884Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486939}

BUG=725605,740044,741047

Change-Id: Ibeee3338455826284044df7695681af319547bad
Reviewed-on: https://chromium-review.googlesource.com/572380Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Yuzhu Shen <yzshen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486938}

The reasons to require are being a LayoutBox, and either having
overflow clip or needing a resizer.

Bug: 467721
Change-Id: If79f1855dfaed6dc60ebd86a2d7e02ebbc1c382d
Reviewed-on: https://chromium-review.googlesource.com/568904
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486937}

Reason for TBR: sheriffing, making the tree green

TBR: suzyh
Bug: 743009
Change-Id: I3cceb99b3fa73bec5b4940f3f3f39ab737130a67
Reviewed-on: https://chromium-review.googlesource.com/572334Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486936}

BUG=667892
R=gab@chromium.org

Change-Id: If4c7bdd1a8109a38cf0dc1081234e025e267f217
Reviewed-on: https://chromium-review.googlesource.com/570732Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486935}

There will be one shared block cache for all users of
LevelDB::Init, and a separate one for All IndexedDB
instances. The default is 8MB, but it's 512KB for
low-memory Android devices.

Previously, each instance would get its own block cache, and use
the default LevelDB settings for such a cache, which is 8MB (*)

(*) https://cs.chromium.org/chromium/src/third_party/leveldatabase/src/include/leveldb/options.h?gsn=Options&l=96

Bug: 711518
Change-Id: I6a64467815489ae7695b8db9b9074170d9e56d94
Reviewed-on: https://chromium-review.googlesource.com/567583
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486934}

On Mac it can happen that certain cameras stop working system-wide after Chrome 
has been running for a while (potentially days) and the computer has gone 
through sleep/wakeup cycles.

This could potentially be related to DeviceMonitorMac interacting with 
VDCAssistant either at a bad time or in a bad way. To be able to test this 
theory, this CL adds a feature switch that allows disabling the use of 
DeviceMonitorMac.

Bug: 699446
Test: Run chromium on Mac with --disable-features=DeviceMonitorMac
Change-Id: Id2a06c75bca7ec8e2db37b4b9647fe508edb0327
Reviewed-on: https://chromium-review.googlesource.com/558199Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#486933}