GitLab

https://swiftshader.googlesource.com/SwiftShader.git/+log/be5fe77..9e22c54

BUG=

TBR=kbr@chromium.org

TEST=bots

CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_chromium_cfi_rel_ng;luci.chromium.try:android_optional_gpu_tests_rel

Change-Id: I04b21d621bd44d673798b71536b033025dcada8d
Reviewed-on: https://chromium-review.googlesource.com/1158963Reviewed-by: Alexis Hétu <sugoi@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Alexis Hétu <sugoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579944}

When we restore the scroll position after a model update, we must
refresh the scroll view layout to show the scroll bar in the right
position.

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

Bug: 860037
Change-Id: I1df221b8ec11c212c1fb4db0f7430f9daadaaa54
Reviewed-on: https://chromium-review.googlesource.com/1158995Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579942}

This reverts commit 5b9084f8.

Reason for revert: Reland after trimming out unused SDK features in dex file

Original change's description:
> Revert "[Android MR] Migrate session management"
> 
> This reverts commit 40d02af1.
> 
> Reason for revert: Broke downstream release builders, and caused
> large binary size regression.
> 
> Original change's description:
> > [Android MR] Migrate session management
> > 
> > This CL migrates the session management part of MediaRouter.
> > CreateRouteRequest is not used and we are using route selection
> > to let CAF start sessions automatically.
> > 
> > Change-Id: I58d267418d9afd11f4f44520e8ca8ad94e82388b
> > Reviewed-on: https://chromium-review.googlesource.com/1006358
> > Reviewed-by: David Trainor <dtrainor@chromium.org>
> > Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
> > Commit-Queue: Zhiqiang Zhang <zqzhang@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#569080}
> 
> TBR=dtrainor@chromium.org,zqzhang@chromium.org,tguilbert@chromium.org
> 
> Change-Id: I8fae7d4492f873223b5efb3fc3e5d6acef37f981
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 855081, 855025
> Reviewed-on: https://chromium-review.googlesource.com/1109981
> Reviewed-by: agrieve <agrieve@chromium.org>
> Commit-Queue: agrieve <agrieve@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#569314}

TBR=dtrainor@chromium.org,agrieve@chromium.org,zqzhang@chromium.org,tguilbert@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 855081, 855025
Change-Id: I8fcdf97d32b57f6011be1dbd322365ceeaf3f442
Reviewed-on: https://chromium-review.googlesource.com/1132356
Commit-Queue: Zhiqiang Zhang <zqzhang@chromium.org>
Reviewed-by: Zhiqiang Zhang <zqzhang@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579941}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/b538ae75..0a9c4581

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Iae796f0d9518546f07df16676e98e0f8d3fec652
Reviewed-on: https://chromium-review.googlesource.com/1158803Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#579940}

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file a bug against
gbiv@chromium.org. Additional context: https://crbug.com/805539

The AutoRoll server is located here: https://afdo-chromium-roll.skia.org

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=gbiv@chromium.org

Change-Id: Ic4ff734f03587b3e21cdb1a09082711a9c8fbb91
Reviewed-on: https://chromium-review.googlesource.com/1159266Reviewed-by: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#579939}

This avoid casting CmaBackend insteaces in MediaPipelineBackendManager,
which is unsafe since we don't know the real type.

Change-Id: I82ae529384575f2db5002ab1417de4a056eb3186
Reviewed-on: https://chromium-review.googlesource.com/1159221Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Reviewed-by: Sergey Volk <servolk@chromium.org>
Commit-Queue: Kenneth MacKay <kmackay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579938}

- Stop/Restart Assitant when settings changed;
- Enable Assistant at start of optin flow.
- Hide UI when Assitant is disabled.

Bug: b/110991778, b/111720990
Change-Id: I675ec2b257fdbf8fd7ff2c9bcf9484cc3ea4beb1
Reviewed-on: https://chromium-review.googlesource.com/1150923
Commit-Queue: Yue Li <updowndota@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579937}

Bug: 852541
Change-Id: Ifb5c2cc57b9f4cb7e01183c1ed02fc25005fa32c
Reviewed-on: https://chromium-review.googlesource.com/1159162Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579936}

https://chromium.googlesource.com/catapult.git/+log/59a61beec4fe..68b5e7dbc095


git log 59a61beec4fe..68b5e7dbc095 --date=short --no-merges --format='%ad %ae %s'
2018-08-01 benjhayden@chromium.org Add third_party/gae_ts_mon


Created with:
  gclient setdep -r src/third_party/catapult@68b5e7dbc095

The AutoRoll server is located here: https://catapult-roll.skia.org

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:867060
TBR=sullivan@chromium.org

Change-Id: I2b2ab4079278b5c7adabbd5fcf0a7a188273e6f3
Reviewed-on: https://chromium-review.googlesource.com/1159121Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#579935}

https://skia.googlesource.com/skia.git/+log/e632dfcb362e..def554697b95


git log e632dfcb362e..def554697b95 --date=short --no-merges --format='%ad %ae %s'
2018-08-01 egdaniel@google.com Include windows.h in debug windows vulkan to fix build.
2018-08-01 csmartdalton@google.com Don't change the front face direction in Vulkan
2018-08-01 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader 7f1c3d07e961..9e22c542d6be (1 commits)


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

The AutoRoll server is located here: https://autoroll.skia.org

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=master.tryserver.blink:linux_trusty_blink_rel;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=scroggo@chromium.org

Change-Id: I70927415e71fdc48cda91257280ac3acc3a4bd91
Reviewed-on: https://chromium-review.googlesource.com/1159027Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#579934}

Currently, AsyncTask.execute() defaults to the SERIAL_EXECUTOR. This
exector is good for preventing concurrency errors since it guarantees
serial execution, but bad for performance since the entire app shares
this single queue.

It looks like this callsite can use the THREAD_POOL_EXECUTOR instead,
since this use doesn't appear to rely on the concurrency guarantees that
SERIAL_EXECUTOR provides.

Bug: 869907
Change-Id: Ied05df42799c3b643f61d2db6abaec65d53b110c
Reviewed-on: https://chromium-review.googlesource.com/1158992Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579933}

This crash is an odd one as we only have an optimized stack trace and limited
info since it is from a mini dump.  From best I can tell, this crash is due
to a race condition in the start-up path for the desktop process.  In the dump,
I see the other capturers all being initialized on the other threads so this
is very early on.  It occurs because the start and inject methods related to
Touch are run on different threads.  I looked into sorting that out but it is
a bigger refactor than I would like to do at the moment (there are several
classes and three threads to sort out).

This fix ensures that the InputInjectorWin instance always has a valid
TouchInjectorWin object to call into, even if the touch class has not
been initialized yet (it is likely deferred due to the time and the fact
that we need to load a library from disk).

BUG=869990

Change-Id: Ic408c534e8ee71f4aa9e712f5ffb415ff97222c6
Reviewed-on: https://chromium-review.googlesource.com/1159168Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579932}

We are currently receiving about 300 reports a day.
This CL is moving the frequency by 10x.

R=erikchen

Bug: 867921
Change-Id: I237e73afa929a0b8358b489dee4fef37f552aeda
Reviewed-on: https://chromium-review.googlesource.com/1159166Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579931}

https://webrtc.googlesource.com/src.git/+log/78026754a734..d3b7ec2e911a


git log 78026754a734..d3b7ec2e911a --date=short --no-merges --format='%ad %ae %s'
2018-08-01 jbauch@webrtc.org Allow all "token" chars from RFC 4566 when checking for legal mid names.


Created with:
  gclient setdep -r src/third_party/webrtc@d3b7ec2e911a

The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I3f631a1f666ad8eb8d749f77ec3cfd9f18d80140
Reviewed-on: https://chromium-review.googlesource.com/1159025Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#579930}

The target remoting/test:ar_sample_test_driver is broken because the
//ui/gl dependency is missing (for GL headers) and the GL lib was being
added for the is_chromeos build (the cros chrome-sdk build does not have
libGL).

R=yuweih@chromium.org

Bug: 867013
Test: none
Change-Id: I409d9540ff3cb2ce6cb2c2d570e3441d1f80c7ee
Reviewed-on: https://chromium-review.googlesource.com/1150510
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579929}

https://pdfium.googlesource.com/pdfium.git/+log/ad39141331e5..2563fc3895f2


git log ad39141331e5..2563fc3895f2 --date=short --no-merges --format='%ad %ae %s'
2018-08-01 tsepez@chromium.org Make FPDF_FormHandle be represented as an incomplete type.
2018-08-01 thestig@chromium.org Encapsulate some public static methods in CFXJSE_FormCalcContext.
2018-08-01 thestig@chromium.org Fix assertion in opj_j2k_merge_ppt().
2018-08-01 thestig@chromium.org Refactor PatternStringType().
2018-08-01 thestig@chromium.org Roll third_party/freetype/src/ b532d7ce7..578bcf103 (28 commits)


Created with:
  gclient setdep -r src/third_party/pdfium@2563fc3895f2

The AutoRoll server is located here: https://pdfium-roll.skia.org

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.



BUG=chromium:614691
TBR=dsinclair@chromium.org

Change-Id: Ia0d452e71ddb24a981209c38b55c480b94d7b0e1
Reviewed-on: https://chromium-review.googlesource.com/1159024Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#579928}

Bug: 869495
Change-Id: I96b3eb4e72b3c46b94bdafcbc4daaf0d9466b35b
Reviewed-on: https://chromium-review.googlesource.com/1159175Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579927}

ChromeVox now imports the SRE as a third party library.

Previously, ChromeVox shipped with a large number of unicode translations for English. Much of this is actually already handled by the underlying tts engine, which can also do a better job of localisation (given the right voice is selected).

This change also tries to fix recent Closure compiler errors as of the latest update to Closure compiler.

Change-Id: Idb9362c8760bf0fa6ce0c1a1a03a29c5a7452871
Reviewed-on: https://chromium-review.googlesource.com/1159099Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579926}

We have collected the data we need and found the likely cause of
crashes.

Bug: 794625
Change-Id: I1e730b27e17b916bec6bbbe20b7734f2b81481db
Reviewed-on: https://chromium-review.googlesource.com/1158721Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579925}

Bug: 855193
Change-Id: I2e30bd2e6188a7695b469955c896dd5900fb1793
Reviewed-on: https://chromium-review.googlesource.com/1157545Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579924}

It is possible that the navigation completes in the time it takes to
animate to the tab grid. The navigation completion will trigger another
snapshot. But that snapshot may have the previous webpage because the
rendering is not guaranteed to have been completed at navigation
completion.

This CL implements a pausing/resuming mechanism so that we pause
snapshotting when animating to the tab grid while the webpage was
loading. We resume snapshotting once the animation to the tab grid
has completed.

This CL also fixes the snapshot going blank for a second while
animating to the tab grid.

Bug: 853569, 862799
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ib6f5cf1ca896c06940c7ce142518b94ffb3c7d37
Reviewed-on: https://chromium-review.googlesource.com/1156135
Commit-Queue: edchin <edchin@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579923}

Bug: 866225
Change-Id: I11d97d9a97432a1abb97e69a1395948b9d3e19fe
Reviewed-on: https://chromium-review.googlesource.com/1157290
Commit-Queue: Reid Kleckner <rnk@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579922}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=mmoss@chromium.org

Change-Id: I9cc14f7277eb4ddad9add50a333f106b27b6ebd2
Reviewed-on: https://chromium-review.googlesource.com/1159186Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579921}

Change-Id: I199d5c97e50be57f9dd0ca08e16f75e5c4315e95
Reviewed-on: https://chromium-review.googlesource.com/1157922Reviewed-by: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579920}

Adding estimated memory usage to the quick history provider.
it is suspected to be slow and cause jank on UI thread when memory usage
is high.

These metrics will be received with slow-reports and will help to
investigate some jank on UI thread.

R=mpearson@chromium.org

Bug: 868419
Change-Id: I344f84ec00f318fdb9db63c5b464b119a9d5e3eb
Reviewed-on: https://chromium-review.googlesource.com/1156847
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579919}

When working on out-of-process mojo services it is hard to figure out
which log line comes from which process. Often both the browser process
and the remote process are running shared components (e.g. code in
//ui/views in both out-of-process ash and browser process). Trying to
back-correlate pids with process types is really awkward.

Add a optional prefix to the start of log lines so things look like:
[my_process:80672:80672:0730/151208.285440:ERROR:file.cc(2982)]...

Only add the prefix to new mojo service processes because it's
possible there are consumers of existing browser process logging
and I don't want change the format of existing browser or renderer
logs.

Bug: 869181
Test: added to base_unittests
Change-Id: Ia26a78d69c19e1f5cbf8ecd269e962ad0589d008
Reviewed-on: https://chromium-review.googlesource.com/1156988Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579918}

This did not produce any useful data.

Bug: 863817
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
Change-Id: I9a4923c76b5b4ddf49ba778fb12656b05c42282b
Reviewed-on: https://chromium-review.googlesource.com/1155743Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: ccameron <ccameron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579917}

Currently, AsyncTask.execute() defaults to the SERIAL_EXECUTOR. This
exector is good for preventing concurrency errors since it guarantees
serial execution, but bad for performance since the entire app shares
this single queue.

It looks like this callsite can use the THREAD_POOL_EXECUTOR instead,
since this use doesn't appear to rely on the concurrency guarantees that
SERIAL_EXECUTOR provides.

Bug: 869907
Change-Id: I2f5b412edaf9e6f9ec2e634af757f3b238987afe
Reviewed-on: https://chromium-review.googlesource.com/1159112Reviewed-by: Min Qin <qinmin@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579916}

Currently, AsyncTask.execute() defaults to the SERIAL_EXECUTOR. This
exector is good for preventing concurrency errors since it guarantees
serial execution, but bad for performance since the entire app shares
this single queue.

It looks like this callsite can use the THREAD_POOL_EXECUTOR instead,
since this use doesn't appear to rely on the concurrency guarantees that
SERIAL_EXECUTOR provides.

Bug: 869907
Change-Id: Iad83ebccb137eec01ff32bc1f78d72047859efc8
Reviewed-on: https://chromium-review.googlesource.com/1158789Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Sam Maier <smaier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579915}

This CL updates the SPIRV-Tools DEPS entry. This requires adding a
SPIRV-Headers third_party dependency as the headers are no-longer part
of SPIRV-Tools.

The BUILD.gn file for SPIRV-Tools is added directly to the SPIRV-Tools
repo and so third_party/SPIRV-Tools/BUILD.gn can be removed. The
SPIRV-Tools build contains fuzzing targets which are enabled with this
change.

Change-Id: I9181a1b50c1f08bbe4e68dff0e00b927d297745f
Reviewed-on: https://chromium-review.googlesource.com/1142028
Commit-Queue: dsinclair <dsinclair@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579914}

A minimal FrameSinkVideoCaptureOverlay implementation for browser window
video capture on ChromeOS (i.e., not desktop capture, and not
WebContents capture). The intention is for this code to be a temporary
solution until more work is complete on services/ui/ws (the new Window
Service).

Bug: 810133,806366
Change-Id: I4f929248a9620f96f2a538caaac9761a472cbe09
Reviewed-on: https://chromium-review.googlesource.com/1155985
Commit-Queue: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Xiangjun Zhang <xjz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579913}

- This is a precursor to removing the generic 'Sites' notification
channel - now that we should have a specific site channel for each
origin with notification permission, the sites channel should never be
used, but adding UMA to verify this.

Bug: 802380
Change-Id: I911b569dad291a4a9f01530f1185adc4dbcaa41e
Reviewed-on: https://chromium-review.googlesource.com/1159020
Commit-Queue: Anita Woodruff <awdf@chromium.org>
Commit-Queue: Peter Beverloo <peter@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579912}

In this patch, we make 3 changes to measure pinch zoom latency:
1. Separate touchpad pinch zoom latency info from wheel
2. Add histogram to measure pinch zoom latency from when receiving
   event from system to when sending event to render. This helps us
   understand the latency of waiting synthetic wheel event.
3. Add histogram to measure pinch zoom latency from when receiving
   event from system to when the resulting GPU frame swap completed.
   This helps us understand the latency of the end to end touchpad
   pinch.


Bug: 565980
Change-Id: I304675684746e6d8f6001937264afa0fc9037324
Reviewed-on: https://chromium-review.googlesource.com/1142447Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Jianpeng Chao <chaopeng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579911}

Following bot results are included.
8499 8501 8504 8506 8507 8511 8515 8519 8523 8526 8533 8536
8539 8543 8547

10 lines were removed and 7 lines were deflaked by consecutive
results since 8506.

TBR=eae@chromium.org, mstensho@chromium.org
NOTRY=true

Bug: 591099
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I9e5b22037f39e7eeaedd9c46f1704f18604f553d
Reviewed-on: https://chromium-review.googlesource.com/1155280
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579910}

GetLevelSize calls GLTargetToFaceIndex which asserts if the target is bogus, so move
the early out before this call.

Bug: 868242
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
Change-Id: I24a6262e2f7cf3ebf70c814bfca818365ec6c242
Reviewed-on: https://chromium-review.googlesource.com/1158801Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579909}

Bug: 868552
Change-Id: Iac64b875611994439dae09d65ff7c999cde74ff8
Reviewed-on: https://chromium-review.googlesource.com/1153301Reviewed-by: Robert Kaplow (slow) <rkaplow@chromium.org>
Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Commit-Queue: Jared Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/master@{#579908}

Original CL:

- https://chromiumcodereview.appspot.com/9722025

  Fix virtual memory regression from new tcmalloc: use old kPageShift
  and kMaxSize w/ kNumClasses = 54. (retry of r127301)

  BUG=118329
  TEST=perf tests.
  TBR=jar@chromium.org
  Committed:
  https://src.chromium.org/viewvc/chrome?view=rev&revision=127381

BUG=724399,b:70905156

Change-Id: I491bb82db0e94a71dc7c7b2742f9c4ef47b2eca1
Reviewed-on: https://chromium-review.googlesource.com/1130783Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Gabriel Marin <gmx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579907}

Add recording of AnchorElementMetrics.Clicked.RatioRootHeight.

Bug: 850624
Change-Id: Ia5ff57cc729cf7d577a59967f473c50da99e1e3b
Reviewed-on: https://chromium-review.googlesource.com/1157282Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Lu Chen <chelu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579906}

Bug: 864302, 869221
Change-Id: I29318c89757dbf21ace69a83519d62d237691f2c
Reviewed-on: https://chromium-review.googlesource.com/1139404Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Travis Skare <skare@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579905}