GitLab

We got 1 crash dump for NV12 and 3 for YUY2 all of which are due to OOM.
NV12 failures in UMA seem to be from older clients before the fix for
odd dimensions went in.  Filtering UMA to recent versions shows that
there are no NV12 swap chain creation failures.

Also change default swap chain format to NV12 when overlays are enabled
using command line flags.

Bug: 869677
Change-Id: If847f1d0a6121df27445b99e3bcb62290b3ed5df
Reviewed-on: https://chromium-review.googlesource.com/c/1355616Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612465}

Add a new UMA histograms metrics to record the Assistant query response
type (e.g., new browser tab, inline element).

Test: local compile and manually test.
Change-Id: Ibc8c8e28f1880bc1c748b5c151ab7d6e3ae58cb8
Reviewed-on: https://chromium-review.googlesource.com/c/1318733
Commit-Queue: Meilin Wang <meilinw@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612464}

Follow up to https://chromium-review.googlesource.com/c/chromium/src/+/1345422,
doing a couple of things.

1. Removing the destroy warning comment, as all bridges will need to follow
this pattern indefinitely. It is not a temporary comment, and adds significant
bulk to any bridge that may become out of sync over time.
2. Call consumers/callbacks immediately with error, null, or default responses.
This allows the Feed to take reasonable responses and not hang during shutdown.
3. Fix mistake in scheduler check that was backwards, causing the scheduler to
think it perpetually had an outstanding request.

Bug: 901414
Change-Id: Ied653541755d5fb1b204c4968e755364cdcece81
Reviewed-on: https://chromium-review.googlesource.com/c/1355614Reviewed-by: Filip Gorski <fgorski@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612463}

Fix a few last truncation errors.

BUG=879657

Change-Id: I75339fe7a46efa336bdaa91c73c21a5c673b32f3
Reviewed-on: https://chromium-review.googlesource.com/c/1355856Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612462}

FuchsiaVideoDecoder was calling DecodeCB synchronously in Decode().
DecoderStream doesn't expect this, so it was failing a DCHECK.

Bug: 909018
Change-Id: Ibf445447b3875ae76ff5d69a5ba9af174836a21b
Reviewed-on: https://chromium-review.googlesource.com/c/1351647Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612461}

This is part 3/4 CLs to move the <audio>/<video> elements off of
a synchronous API that can lead to renderer hangs and premature
audio renderer errors.

This moves the AudioRendererSinkCache from AudioRendererMixerManger
to a base::NoDestructor instance in AudioDeviceFactory and stops
ARMM from using the cache at all. The users remaining are WebAudio
and WebRTC, we can reevaluate metrics on keeping it after.

Due to base::(SingleThread|Sequenced)TaskRunner::Get() being
deprecated for content/ I've had to switch to use base::PostTask to
generate a cleanup task runner. Unfortunately this doesn't guarantee
that it runs on the render thread, but since we're now using a static
instance, we can just always use base::Unretained and drop the WeakPtr
factory that was handling the cancellation of these tasks.

There's no point in the cache for ARMM since we're going to require
a sink to get a mixer. That sink will always be used to get output
device info first too and then reused for the mixer.

BUG=905506
TEST=updated tests, compiles.
R=olka

Change-Id: I03408753f974e4c6fb9c89270508e26689162002
Reviewed-on: https://chromium-review.googlesource.com/c/1347730
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612460}

Fix two problems:
1. While focused, mouse move in and move out, control won't hide.
2. While focused, mouse move in and stay, control won't hide after 3 seconds.

Bug: 909087
Change-Id: I4a2c009758e36fd7f3cec5dd9f8042773cc6d454
Reviewed-on: https://chromium-review.googlesource.com/c/1354573Reviewed-by: Tommy Steimel <steimel@chromium.org>
Commit-Queue: Jazz Xu <jazzhsu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612459}

I just realized I had asked back in May whether anyone still uses
legacy-results.html, and nobody replied, so I think it's now safe
to remove this.

Context:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/9NFDSTEzcd4

Bug: 748628
Change-Id: I21e7d7451f3fa2e421daeb08e50a446e1e0a3253
Reviewed-on: https://chromium-review.googlesource.com/c/1355480
Commit-Queue: Quinten Yearsley <qyearsley@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612458}

This patch makes WebContentsViewAura manage its web content's visibility
state based on its current mirror window's occlusion state. To achieve
this, the patch makes the following changes:
 - Adds a new callback in WindowObserver to receive occlusion state
   changes.
 - Creates a subclass of aura::WindowObserver to manage mirror window
   occlusion states for the WebContentsViewAura.
 - Replaces a DCHECK with an early return when an already tracked window
   is requested to be tracked again.
 - Replaces the boolean window property of mirror window with a vector
   list of mirror windows.
 - Updates the unittest and adds a new method to WindowTestApi.

Bug: 901555
Change-Id: I70566c544def6129c7410af84f91e6501a5479d5
Component: Window Mirror View, web contents, Window occlusion tracker
Reviewed-on: https://chromium-review.googlesource.com/c/1313753Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612457}

Bug: 909056
Change-Id: Ib01e78bae85986196f6b2aa03816cdcb2faaa650
Reviewed-on: https://chromium-review.googlesource.com/c/1351974Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612456}

Bug: 909056
Change-Id: I921d0807bf9cf84874664ab89e9a68a60aca4cd5
Reviewed-on: https://chromium-review.googlesource.com/c/1355022Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612455}

Bug: 714962
Change-Id: I6c483d176f4cf2189a15bd7d7ca3f1a452696adc
Tbr: kojii@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/1355988Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612454}

Bug: 909056
Change-Id: Ic44a7ba350b852fcdd0a2983125c7239dc8d7a1a
Reviewed-on: https://chromium-review.googlesource.com/c/1351328Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612453}

MessageLoop will go away, eventually.

BUG=891670

Change-Id: Ifdf986c9fa4b0fd1b6de3c7f907aae9a3672894b
Reviewed-on: https://chromium-review.googlesource.com/c/1352425Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#612452}

Bug: 854346
Test: the new test case
Change-Id: I5a78d4037ffcf2daf995c2fc04ef44459abbd21c
Reviewed-on: https://chromium-review.googlesource.com/c/1338187
Commit-Queue: Jun Mukai <mukai@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612451}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9dbf638d6f75..a8224556fcd5


Created with:
  gclient setdep -r src-internal@a8224556fcd5

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=mmoss@chromium.org

Change-Id: I8e28d640de4f002191ab2e1f70a8ec65e935b15e
Reviewed-on: https://chromium-review.googlesource.com/c/1356003Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#612450}

This reverts commit 99590e1f.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> DevTools: fixed scheduleStepInto for Node 8.x
> 
> Node 8.x does not support breakOnAsyncCall param of
> Debugger.stepInto method.
> 
> R=​dgozman@chromium.org
> 
> Bug: none
> Change-Id: I0e59e0a3742b85a2fd466ac1bac5f7b75aa7f841
> Reviewed-on: https://chromium-review.googlesource.com/c/1352533
> Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
> Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#612075}

TBR=dgozman@chromium.org,kozyatinskiy@chromium.org

Change-Id: Id375af68281dd1316f907f2ea0ee9cfd07b3390e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: none
Reviewed-on: https://chromium-review.googlesource.com/c/1356126Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612449}

Bug: b/117793081
Test: Manual Test
Change-Id: If747d3317cb163715ff907839203e0c0eee57a1c
Reviewed-on: https://chromium-review.googlesource.com/c/1352341
Commit-Queue: Yue Li <updowndota@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612448}

MessageLoop will go away, eventually.

BUG=891670

Change-Id: I9d8c29ddf02aee41b2c2f706dca49b60763ea0a2
Reviewed-on: https://chromium-review.googlesource.com/c/1353883Reviewed-by: Filip Gorski <fgorski@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#612447}

Remove the in-cell text from the sub-pixel-border-2.html reference test
to avoid rounding and subpixel alignment issues for the text content.

Bug: 591099
Change-Id: I5c3f7b7c42f13931d44a36f87b7ebc651169769c
Tbr: mstensho@chromuim.org
Reviewed-on: https://chromium-review.googlesource.com/c/1355991Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612446}

https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/8ce3dbabb8b5..2cd040b0d342


git log 8ce3dbabb8b5..2cd040b0d342 --date=short --no-merges --format='%ad %ae %s'
2018-11-29 zoddicus@users.noreply.github.com Merging two ValidateMemoryScope implementations (#2132)
2018-11-29 stevenperron@google.com Don't inline recursive functions. (#2130)


Created with:
  gclient setdep -r src/third_party/SPIRV-Tools/src@2cd040b0d342

The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-tools-chromium-autoroll

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=dsinclair@chromium.org

Change-Id: I636d055fc33387f9497bfd03e21b5bfd9e22d553
Reviewed-on: https://chromium-review.googlesource.com/c/1355847Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#612445}

In the current implementation, it's possible to create inconsistency while
a node waiting to be assigned with a swap time is removed. When this happens,
the detector still creates a record of the removed text, but it shouldn't, as
the created record could become the candidate metric result.

The cause is that when a record is assigned with a swap time, there is no check
of whether the node has been removed.

To fix this issue, we should mark the node as deleted when the node is removed
from the dom tree, and add the checking of validity when we assign the swap time
to the record.

The CL implements this fix.

Bug: 869924
Change-Id: Ie331d40fbad585cf32828c1b99136056d429c5b0
Reviewed-on: https://chromium-review.googlesource.com/c/1354130Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612444}

https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/eb9630f2312f..908e07846946

$ git log eb9630f23..908e07846 --date=short --no-merges --format='%ad %ae %s'
2018-11-16 aoldemeier login: Add DBus call to SessionManager to clear check_enrollment flag.
2018-11-26 xiaochu imageloader/system_api/dlcservice: move constants to system_api
2018-11-22 peah system_api: Add group ID for system AEC
2018-11-08 itspeter runtime_probe: the skeleton

Created with:
  roll-dep src/third_party/cros_system_api
R=derat@chromium.org

Change-Id: I4cd0cb0d357330d69a4a870bcbd45b26c8f03aad
Reviewed-on: https://chromium-review.googlesource.com/c/1355943Reviewed-by: Dan Erat <derat@chromium.org>
Commit-Queue: Per Åhgren <peah@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612443}

Adds a UMA use counter to IDBFactory.databases().

Bug: 909000
Change-Id: I3a45c7cccec208fa8d9227bcfb2cc24a4a688324
Reviewed-on: https://chromium-review.googlesource.com/c/1352484Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Andreas Butler <andreasbutler@google.com>
Cr-Commit-Position: refs/heads/master@{#612442}

Use ScopedTaskEnvironment instead of MessageLoop in
favicon_service_impl_unittest.cc

MessageLoop will go away, eventually.

BUG=891670

Change-Id: I05f9b446058cdfe5e649e821fc8d87ac3e6ec764
Reviewed-on: https://chromium-review.googlesource.com/c/1352365Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#612441}

Changelog
https://chromium.googlesource.com/external/github.com/cisco/openh264/+log/3b51f16a4a41df729f8d647f03e48c5f272911ff..6f26bce0b1c4e8ce0e13332f7c0083788def5fdf

BUG=893594
TBR=mflodman,hbos

Change-Id: I15409f2d1671f23fb785d63f1d3b2f1b0d4b5316
Reviewed-on: https://chromium-review.googlesource.com/c/1355253Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612440}

Bug: 908988
Change-Id: Iaaee8124c56945a8769e6d4ff2a0859ef39c1aea
Reviewed-on: https://chromium-review.googlesource.com/c/1355424Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612439}

Do not assign zero distance to all GC root objects.
Instead assign zero to the global root and follow strong roots only
from there.

BUG=906847

Change-Id: Iee22162ac11a6700e019276daee1357ef33e61b9
Reviewed-on: https://chromium-review.googlesource.com/c/1353995
Commit-Queue: Alexei Filippov <alph@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612438}

Change-Id: I6972a8214f1402f21efe8f7afa35c8f135c996d0
Reviewed-on: https://chromium-review.googlesource.com/c/1351976Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Nigel Tao <nigeltao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612437}

With voice search bar removal and the tab cleanup this method is not used anymore
deleted it and updated unittests.


Bug: 778416
Change-Id: Ia6a130f50eafb01b0eef265e98ca412071ba7b95
Reviewed-on: https://chromium-review.googlesource.com/c/1355765Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612436}

Otherwise setting pdf_enable_v8=false breaks chrome build.

Change-Id: I86c3d369b4142ad05a986363839cbc6961772bc9
Reviewed-on: https://chromium-review.googlesource.com/c/1356010
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612435}

Adds the ability to check for corruption via an IsCorrupt() function
that's pure virtual on the ProtoDatabase. IsCorrupt() is also introduced
in the ProtoLevelDBWrapper, and the corruption flag gets set on the Init
callback after checking status.

Unit tests changed slightly because the init callback needed to be put
into ProtoLevelDBWrapper instead of outside so it could modify
is_corrupt_, and the new use of the WeakPtr caused a race condition that
meant the test always failed to trigger the callback if we don't wait
for init to complete.

Bug: 870813
Change-Id: Ib00435dae8cdac490053fbfc6befb95094b1edec
Reviewed-on: https://chromium-review.googlesource.com/c/1355521
Commit-Queue: Troy Hildebrandt <thildebr@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612434}

Change-Id: Icd07e1501d11914209048081496ca414d58a1f71
Reviewed-on: https://chromium-review.googlesource.com/c/1356023Reviewed-by: Joe Downing <joedow@chromium.org>
Commit-Queue: Gary Kacmarcik <garykac@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612433}

Add total_length() and NumSlices() methods to QuicMemSliceSpan so that length of HTTP/3 data frame can be computed in QuicSpdyStream::WriteBodySlices().

no behavior change.

Merge internal change: 222285071

Change-Id: Ie3e2a120fc072a9d8329e33fe5cef778aa454c39
Reviewed-on: https://chromium-review.googlesource.com/c/1351584Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Renjie Tang <renjietang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612432}

Change-Id: I84983d2fe371ffbf0d6bdbbbf116de532fa741c7
Reviewed-on: https://chromium-review.googlesource.com/c/1340599
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612431}

Change-Id: I390ffca8cb3273fc6e475695a3eeceb6324f741d
Reviewed-on: https://chromium-review.googlesource.com/c/1354649
Commit-Queue: Jazz Xu <jazzhsu@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612430}

This also increased the timeout for test because it can take longer on asan.

TBR=hiroshige@chromium.org, xiyuan@chromium.org

Bug: 910303, 910105
Test: OcclustionTest is skipped in single process mash
Change-Id: I669d7343255980dd540c98aa645e5f14c641c371
Reviewed-on: https://chromium-review.googlesource.com/c/1355883Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612429}

This moves the majority of the MultiUserWindowManagerDelegate functions
into the mojom. For classic mode, a mojo::Binding is created so that notification
happens async (just as it will in multi-process mdoe).

MultiUserWindowManagerWindowDelegate has been removed.

MultiUserWindowManagerDelegate has been removed.

Adds MultiUserWindowManagerDelegateClassic. Here's the comment for it:
// Delegate used in classic and single-process mash mode. This delegate is
// notified when the state of a window changes. In classic mode, this delegate
// is called for all windows, in single-process mash mode, this delegate is
// called for Windows created in ash's window hierarchy (more specifically,
// Windows whose aura::Env has a mode of aura::Mode::LOCAL). For example, Arc
// creates Windows that are parented directly to Ash's window hierarchy, changes
// to such windows are called through this delegate.

Ideally MultiUserWindowManagerDelegateClassic wouldn't be necessary, but that
would require assigning unique ids for local windows, which would be rather
error prone.

The biggest change here is that MultiUserWindowManagerChromeOS is now notified
async of the functions that were in MultiUserWindowManagerDelegate, even in
classic.


BUG=875111
TEST=covered by tests

Change-Id: I51e8a89ae3c4e6096d0cf04dc91133781b8cb4cf
Reviewed-on: https://chromium-review.googlesource.com/c/1354558
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612428}

Bug: webrtc:8671
Change-Id: Ie1d02c21a5c9d1e53b17f929750bd0ed43785dfa
Reviewed-on: https://chromium-review.googlesource.com/c/1355166Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Per Åhgren <peah@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612427}

MyFiles is being changed to allow users to create files/folders, this CL
changes Wallpaper to be able to scan images in MyFiles instead of
Downloads.
The function |MyFilesFolderForProfile| takes care of returning Downloads
path if the flag MyFilesVolume is disabled.

Tested manually by loading in a device with MyFilesVolume flag enabled.

Bug: 873539
Change-Id: If0e40cd1d2961ec5ca380a799c5a272823c0cede
Reviewed-on: https://chromium-review.googlesource.com/c/1353031Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Luciano Pacheco <lucmult@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612426}