GitLab

While the idea in
https://chromium-review.googlesource.com/c/chromium/src/+/1544880 was
correct, we forgot to consider what happens when a source stops and is
disconnected to the ScriptProcessorNode (AudioWorkletNode).  In this
case, the output of the node is disabled.  But that's incorrect in
general because the node's processing must continue because it has
user-defined outputs so a silent input does not imply a silent output.

Rather than adding a special case in DisableOutputsIfNecessary, let's
just revert the change.  The internal properties aren't exposed to the
developer.

Bug: 959125
Test: the-scriptprocessornode-interface/simple-input-output.html
Change-Id: I0f217be24eacff6031a537086df535e6c1e8d9d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598427Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657447}

Specify the custom background image via a <link rel="preload"...>
tag that's inserted at the time the page is served.

Bug: 853042
Change-Id: Id24b1815c66b32f04b1811e55c54b5066cfc9873
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592122Reviewed-by: Dan Beam <dbeam@chromium.org>
Reviewed-by: Kristi Park <kristipark@chromium.org>
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657446}

The new condition is the same as cc::PropertyTreeBuilder.
This avoids unnecessary PAC::Update in js_poster_circle benchmark.

Bug: 954520
Change-Id: Ib547c828d4dee7e97fe8e72e2ed69f7a2545d63c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597209
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657445}

This involves updating the shard number in bot_platforms.py and perf_data_generator.py,
and running the following commands to update the json files:

./tools/perf/generate_perf_sharding update --builders android-nexus5x-perf-fyi
./tools/perf/generate_perf_data


Bug: 959997
Change-Id: I83c028942493742f877385b59d5119fe998abe2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598174
Commit-Queue: Haiyang Pan <hypan@google.com>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657444}

Avoids including assets/unwind_cfi in measurements, which is a canary &
dev-only feature.

Bug: 960197
Change-Id: I513f152ef0172804daaa563d5221eb501b2126f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598230Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657443}

It's unclear why, but we're suddenly hitting this error anytime we try to
upload accessibility changes:

ui/accessibility/PRESUBMIT.py had an exception.
invalid syntax (<string>, line 249)
Maybe your depot_tools is out of date?

NOTRY=true

Bug: none
Change-Id: Iac101d64cb971cd5ac32ad6a90db1d3f657caeb5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600077
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Kevin Babbitt <kbabbitt@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#657442}

This class is no longer needed.

Bug: 960392
Change-Id: If2a6bf13fad036c4133324df1ad41e00a4545439
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598200Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657441}

We capitalise PIN elsewhere so this change aligns the UI with that.

Change-Id: I75c2aadbc29d6687806bf44af88a31012c394f88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598336
Commit-Queue: Adam Langley <agl@chromium.org>
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Auto-Submit: Adam Langley <agl@chromium.org>
Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Cr-Commit-Position: refs/heads/master@{#657440}

Instead of maintaining two separate data structures (a bitmap) and an unordered
hashmap for updating interior slots, just keep track of interior slots in a
std::map.

- std::map::lower_bound is used to provide the bailout that was provided by the
  sparse bitmap.
- The iteration through the objects payload can just be done via iterator
  increment.

Change-Id: I569bd9155bf90bdf300104e8dc2d8ae2dd0dcb63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1595873
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657439}

are in "Incognito" or "guest" mode.

Bug: 958054
Change-Id: I35e4adec0fd1800cff1ec2fcfe7983e2a65540e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1591886
Commit-Queue: Siye Liu <siliu@microsoft.com>
Reviewed-by: Yohei Yukawa <yukawa@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657438}

New Win10 NVIDIA GTX 1660 bot is failing on 2 tests that are missing
expectations.

Bug: angleproject:3424
Tbr: kbr@chromium.org
Change-Id: I0cee6259845a4946aa11a9226f9bd082faa73c1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1600033Reviewed-by: Jamie Madill <jmadill@chromium.org>
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657437}

Bug: 954907
Test: none
Change-Id: Id6fc0782fee4cb259aa5002043fcf4466a91f1d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598482Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657436}

Bug: 945478
Change-Id: I98697e7c8a4f850c9816d1b1b5acd1563e5cd405
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593865Reviewed-by: Chris Lu <thegreenfrog@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657435}

https://chromium.googlesource.com/angle/angle.git/+log/e76c5c3c3246..84e7932d2737


git log e76c5c3c3246..84e7932d2737 --date=short --no-merges --format='%ad %ae %s'
2019-05-07 jonahr@google.com Roll SPIRV Deps (May 7th, 2019)
2019-05-07 syoussefi@chromium.org Vulkan: add uniform buffer object support


Created with:
  gclient setdep -r src/third_party/angle@84e7932d2737

The AutoRoll server is located here: https://autoroll.skia.org/r/angle-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.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=jonahr@chromium.org

Change-Id: Ic340c479b9b8dc3211259abd3254cf445b46c1cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598216Reviewed-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@{#657434}

Fix the test to pass on Mac 10.13.

Bug: 925517
Change-Id: Ifc630605dfd8de124a3d4af77d35f4374ca0c316
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597910Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657433}

Texture::Buffer is using the deprecated ContextFactoryObserver interface
to find out about main thread context loss. The ContextFactory adds
itself as a ContextLostObserver, then on context loss forwards that
message along to all the ContextFactoryObservers.

There are multiple message pipes between the browser and GPU process
that have indeterminate ordering for when they find out about connection
errors. This leads to the following ordering problem:

1. The GPU process crashes. The old shared main thread
   RasterContextProvider is lost and any message pipes between the
   browser and GPU process will encounter connection errors.
2. A new shared main thread RasterContextProvider is created.
3. Exo allocates a new Buffer::Texture using the new shared main thread
   RasterContextProvider.
4. The new Buffer::Texture adds itself as a ContextFactoryObserver.
5. All ContextFactoryObservers get notified about OnLostSharedContext()
   for the old shared main thread RasterContextProvider loss. For the
   new Buffer::Texture this is wrong, the RasterContextProvider is still
   valid.
6. The new Buffer::Texture destroys all of it's resources incorrectly.
   This triggers a flood of GL errors from the GPU process.

Make Buffer::Texture a ContextLossObserver instead. This way the
Buffer::Texture gets notified about context loss for only the
RasterContextProvider it's using.

Bug: 954151, 944597
Test: BufferTest.OnLostResources
Change-Id: Ic68dbaab8864b835b2bbb83b3b43f03495902aef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597390
Commit-Queue: kylechar <kylechar@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657432}

https://skia.googlesource.com/skia.git/+log/06e14afaa7db..056944747072


git log 06e14afaa7db..056944747072 --date=short --no-merges --format='%ad %ae %s'
2019-05-07 halcanary@google.com experimental/editor: progress
2019-05-07 ethannicholas@google.com more SkSL interpreter performance work
2019-05-07 bungeman@google.com Fix some documentation for SkFont.


Created with:
  gclient setdep -r src/third_party/skia@056944747072

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=robertphillips@chromium.org

Change-Id: I271c385dc25d09a24ec41444dfb1cd85d3b17131
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599518Reviewed-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@{#657431}

History observers do not provide notifications on each visit removal.
Instead they provide observers updates when an enitre URLRow is removed.

Bug: 1531691
Change-Id: I92831d6b67698cfb9d8012e47cd3c17d55e1c570
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594658
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Reviewed-by: sebsg <sebsg@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657430}

TBR=tsepez@chromium.org

Bug: 958154
Change-Id: I21dadda1bd78fbd713eb3574edea7f2087100762
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1595982
Commit-Queue: Evan Stade <estade@chromium.org>
Auto-Submit: Evan Stade <estade@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657429}

We are enabling FTL signaling by default to allow easier testing and
debugging.

Change-Id: Id7ea6e9dafa79ad40e2398674fca917ded59033d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598346Reviewed-by: Joe Downing <joedow@chromium.org>
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657428}

Bug: 958152

Change-Id: I5ad52e1829c6698fa0042ef1ab9e4588d45c6e1f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1596839Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Commit-Queue: Fred Mello <fredmello@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657427}

Adds the concept of observers to KerberosCredentialsManager with one
function to notify when Kerberos accounts were added or removed. This
will be used to refresh the Kerberos Accounts UI.

Also removes dependencies on AccountManager since Kerberos accounts get
their own UI. The original plan was to put them into the Account Manager
UI.

BUG=chromium:952237
TEST=None.

Change-Id: If0d6941582cabdca6ec88b36c1b88f5d617ae568
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1588253
Commit-Queue: Lutz Justen <ljusten@chromium.org>
Reviewed-by: Kush Sinha <sinhak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657426}

Now that we've disabled the build warnings for unrar, I can remove the
patches and rollback the changes that existed solely to suppress those
warnings.

Since not every change to 5.6.8 was captured in a patch file, I created
a new patch file including all of the changes we made. There are no
longer that many changes, so I kept them all in one patch.

This CL will be the worst of the three when updating unrar. Luckily it
puts us in a much nicer state, where there are only 48 distinct changes
made to unrar src. Most of the changes to unrar source falls into one
of the following categories:

1. Removing the third_party_unrar namespace
2. Removing parentheses that weren't in the original 5.6.8
3. Removing curly braces around if statements that weren't in the
   original 5.6.8
4. Removing default behavior from non-exhaustive switch statement
5. Adding unused functions back in

The one meaningful change under unrar/src is the change to
unrar_wrapper.h. The forward-declared symbols are now in the top-level
namespace, rather than the third_party_unrar namespace, so I declare
them as such.

Bug: 936112
Change-Id: Icce266b0e685494cd425bb8c886c2f8f3b826d99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592463
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657425}

This apparently saves about 90k of size, though it does potentially
make for larger differential updates.

Bug: 958522
Change-Id: Ibcf79739ff6d1cf734aa9649080f5be754d1200e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597126Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657424}

This new OOBE/Login page will handle custom setup needed for
supervised/child accounts. At the moment this version does nothing and
simply shows a placeholder screen. It will only be shown if the user
has the "EnableSupervisionOnboardingScreens" feature enabled.

Bug: 958995
Change-Id: I2ddec65ddd25d7850a04b166ba332a86e47688e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594112
Commit-Queue: Lucas Tenório <ltenorio@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657423}

Change-Id: I4135a98530993749d653c23e26015096e8de0556
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597963
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Reviewed-by: Jeffrey Cohen <jeffreycohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657422}

https://swiftshader.googlesource.com/SwiftShader.git/+log/60a6a2e77188..c958b17184e6


git log 60a6a2e77188..c958b17184e6 --date=short --no-merges --format='%ad %ae %s'
2019-05-07 bclayton@google.com LLVMReactor: Assert return value type matches function sig.


Created with:
  gclient setdep -r src/third_party/swiftshader@c958b17184e6

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG=chromium:b/131914569
TBR=swiftshader-team+autoroll@chromium.org

Change-Id: I561926ecb9eaa81d9ead7e3364a47f2273b2a0ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599519Reviewed-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@{#657421}

It no longer simulates what happens with the window-service, rather it creates
a widget and/or window depending upon the parameters.

BUG=958062
TEST=test only changes

Change-Id: I132fd975209ad0a4dd268e934359e123cc4ab983
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599875Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657420}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
TBR=cr-fuchsia+bot@chromium.org

Change-Id: Iaee2efb9da0ddfc5a5a62168ff7bddb266716af6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598217Reviewed-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@{#657419}

ScopedTaskEnvironment::ExecutionMode is becoming
ScopedTaskEnvironment::ThreadPoolExecutionMode

This CL was uploaded by git cl split.

R=dougarnett@chromium.org

Bug: 708584
Change-Id: I834591a69bd1ffa8c87c73c7a890a92971b8f91d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1583791
Auto-Submit: Carlos Caballero <carlscab@google.com>
Reviewed-by: Doug Arnett <dougarnett@chromium.org>
Commit-Queue: Carlos Caballero <carlscab@google.com>
Cr-Commit-Position: refs/heads/master@{#657418}

This will be used to support pixel test framework for desktop ui.
Summary: the framework can be used for browser_test to write pixel tests.
The image diff webui is provided by Skia Gold.
Design doc(Internal):
https://docs.google.com/document/d/1Mz72RHWyQKsT6jynrDNGbCaTKQIy_77qMjRM5gpsr_w/edit?usp=sharing
Design doc(Public):
https://docs.google.com/document/d/1uvXp0AKfemJ9e1TXM1nH3UTcVlDKISK2jFd_g2gstX0/edit?usp=sharing

Bug: 958242
Change-Id: I2991597ed82621710555ccb2fac59b2e88511e6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1589685
Commit-Queue: Sven Zheng <svenzheng@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657417}

Store the associated ActionInfo::Type on the ActionInfo object. This is
in preparation for reducing the number of places that need to call
Get[Page|Browser]Action directly, and allowing them to query the type
if and only if they really need it.

Bug: 893373

Change-Id: Ia0564de55c8e052460b4c3991081eeb6ccab4ecf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1575729
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657416}

To limit regression in the total analysis time from Safe Browsing,
cutoff DMG analysis at 10 seconds. Future CLs will institute similar
timeouts for ZIP and RAR archives.

Bug: 948277
Change-Id: Iff7dabfdecc1791d5a83e36dc34a8c57ed99fd9e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594166Reviewed-by: Nathan Parker <nparker@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657415}

Also, add problemMatcher items for generated files.

Change-Id: I610e280fc5874478b56c9de8de46d36498fe393d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1552041Reviewed-by: Chase Phillips <cmp@chromium.org>
Reviewed-by: Darwin Huang <huangdarwin@chromium.org>
Commit-Queue: Darwin Huang <huangdarwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657414}

rather than the TracingController.

This is in preparation for being able to handle proto traces
in addition to JSON.

R=ssid@chromium.org
BUG=925151

Change-Id: I91ed3c9648587fb19a5102b869a5d5ab688e0187
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546146
Commit-Queue: oysteine <oysteine@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: ssid <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657413}

There are some functions missing and the tests may cause memory leak. I
have fixed them and now removed them from "web_tests/TestExpectations."

Bug: 959168
Change-Id: I844de221c05357b7df52aa71d72bd7ca6f3497bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597229Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657412}

The ForcedStyleAndLayout metric is very very high under the new sampling
approach. The root cause is JS being scheduled outside of the main frame
period, in which case we keep adding up the JS time but never reset it
until a main frame actually happens and we record.

This patch should improve things by resetting even when we are not
in a begin main frame block, forcing the ForcedStuyleAndLayout timers
to reset even if no lifecycle work was done on that frame.

Bug: 959798
Change-Id: Icdd107f04444b7780a7f28158598b3ccddb70d7b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599773
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Auto-Submit: Stephen Chenney <schenney@chromium.org>
Reviewed-by: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657411}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/b5ac6664419e..bebc1e506803


git log b5ac6664419e..bebc1e506803 --date=short --no-merges --format='%ad %ae %s'
2019-05-07 dhanyaganesh@chromium.org cidb.py: fix for broken uprevchrome tool


Created with:
  gclient setdep -r src/third_party/chromite@bebc1e506803

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-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.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel
TBR=chrome-os-gardeners@chromium.org

Change-Id: I989b79339a81d3a77110e6532ea2bd3d3e800fff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598511Reviewed-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@{#657410}

Set this field in MediaPipelineDeviceParams when create backend in
CastRenderer.

Bug: internal b/110233576
Test: 1) together with an internal CL, verified OEM and mixer backends
can be created. 2( Internal CQ.

Change-Id: Icc31d509c7d6d965ac35fe2f50fa8c5374dd0af2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1592172Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Reviewed-by: Sergey Volk <servolk@chromium.org>
Commit-Queue: Guohui Deng <guohuideng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657409}

I'll follow up and remove the arg once downstream references are
removed.

Change-Id: I2f431bcab8d5f6842603c3b29b31672ac757f030
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1598193
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657408}