GitLab

This CL enables DMA-buf encoding on VAAPI JEA to optimize the
performance and reduce the CPU consumption.

Bug: 944705, b/123057886
Test: Manually
Test: ./jpeg_encode_accelerator_unittest

Change-Id: I05d80c8bb649b0c09ad26d3545377c77e3d385bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1532135
Commit-Queue: Wei Lee <wtlee@chromium.org>
Reviewed-by: Ricky Liang <jcliang@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Tommi <tommi@chromium.org>
Reviewed-by: Sheng-hao Tsao <shenghao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662964}

WaitForVBlank returns very early when the monitor goes to sleep.
Fallback to Sleep() if that happens.

Bug: 965936
Change-Id: I4df347d56a3ec12c02ae398a9b9325c93845fb44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628159
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662963}

This reverts commit c95749d2.

Reason for revert:
Some web_tests are crashing due to this change.
https://test-results.appspot.com/data/layout_results/WebKit_Linux_Trusty_ASAN/26566/webkit_layout_tests/layout-test-results/results.html

Original change's description:
> Worker: Abort all inflight tasks in Worklet::ContextDestroyed()
> 
> Before this CL, all inflight tasks can be retained in
> Worklet::pending_tasks_set_ even after context destruction, and that causes
> dcheck failures in the destructor of Worklet. This CL fixes it by aborting them
> in Worklet::ContextDestroyed().
> 
> In addition, this CL adds test coverage of addModule() calls on a detached
> iframe. In the tests, LayoutWorklet is used for testing main thread worklets
> instead of PaintWorklet because PaintWorklet will be switched to
> off-the-main-thread worklets (see https://crbug.com/829967).
> 
> Bug: 962355
> Change-Id: I7da71e7f4bdcbfa20125853832122a733c118a7a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626062
> Reviewed-by: Matt Falkenhagen <falken@chromium.org>
> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#662923}

TBR=falken@chromium.org,nhiroki@chromium.org

Change-Id: I54041a299dfdc74ff298b001cd42609fe2c11901
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 962355
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627843Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662962}

In order to support moving CacheStorage off the IO thread and on to
a separate SequencedTaskRunner, we are encapsulating the threading
requirements.  This CL does this by removing the requirement that
external clients of CacheStorageContext must be on the IO thread.
Instead the API can be accessed directly on the UI thread and
CacheStorageContextImpl will handle executing the code on the correct
sequence.

Bug: 960012
Change-Id: I7d576a7deb484113cff0e9454b038f7b87c5e503
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625971Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662961}

Off-the-main-thread shared worker script fetch depends on PlzSharedWorker
(NetworkService). Therefore, even after this CL, on-the-main-thread shared
worker script fetch is still used in some platforms where PlzSharedWorker
(NetworkService) has not been enabled by default yet.

Bug: 924041
Change-Id: Ic2282fc69b4af666932fcf35a0375e25a88ac052
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535499Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662960}

This page is useful for debugging so it should appear at about:about.
Also update the comment explaining how to do so.

Bug: None

Change-Id: I5c0ecac337381315ca8427d7046831f0f00275e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627855Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662959}

https://html.spec.whatwg.org/multipage/forms.html#dom-form-requestsubmit

Intent: https://groups.google.com/a/chromium.org/d/msg/blink-dev/CxelaeahNho/aC6Zp8KvAwAJ

Bug: 964062
Change-Id: Iea72587605c8f1c13c98b05be3b7d971c9fe7543
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1616924
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Keishi Hattori <keishi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662958}

This CL adds following flags to show "from prefetch cache" in DevTools.
  - ResourceResponseInfo.was_in_prefetch_cache
  - WebURLResponse::SetWasInPrefetchCache()
  - blink::ResourceResponse
      ::WasInPrefetchCache()
      ::SetWasInPrefetchCache()
  - Response.fromPrefetchCache in browser_protocol.pdl
  - SDK.NetworkRequest
      .SetFromPrefetchCache()
      .fromPrefetchCache()
And checks fromPrefetchCache() in NetworkDataGridNode.js to show
"(prefetch cache)" in DevTools' Network tab's data grid, and in
RequestHeadersView.js to show "(from signed-exchange prefetch cache)" in
DevTools' Network tab's request header's view.

TBR=caseq@chromium.org,pfeldman@chromium.org

Bug: 935267
Change-Id: Ia026f586f65a021089eafde09b77f6364754c38e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1619527
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Alexei Filippov <alph@chromium.org>
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662957}

Update the parameterized declarativeContent tests to exercise the
behavior with the "action" manifest key, in addition to the page and
browser action keys.

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

The constructor of mojo::InterfacePtr that takes InterfacePtrInfo used
to call InterfacePtr::Bind without TaskRunner. That causes the default
task runner usage, which is discouraged.

This adds a SequencedTaskRunner parameter to align InterfacePtr::Bind.

Change-Id: I07cf911a6110f078d3bf128edc905dc1ac960c69
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1621802Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662955}

https://chromium.googlesource.com/catapult.git/+log/63ab0c82ecf5..65790b717589


git log 63ab0c82ecf5..65790b717589 --date=short --no-merges --format='%ad %ae %s'
2019-05-24 dberris@chromium.org Pinpoint: Add dberris@ to OWNERS
2019-05-24 dberris@chromium.org Pinpoint: Fix comparison to handle None sentinel


Created with:
  gclient setdep -r src/third_party/catapult@65790b717589

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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:966328
TBR=eyaich@google.com

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

Bug: 965307
Change-Id: I57e35104a748ff5194a556ba212974114d2e59be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627431Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662953}

Bug: 966555
Change-Id: Ib75128520a9f20f68e336beee6d8e63b1e81bd29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627820
Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662952}

"MimeHandlerView" is a chrome/extensions layer term and should not leak
into blink or content layers. This CL renames public APIs for creating
a MimeHandlerView uses terms "external plugin" and
"handle externally" when appropriate. The change is purely mechanical.

TBR=haraken@chromium.org, dcheng@chromium.org, jam@chromium.org, creis@chromium.org

Bug: 659750
Change-Id: Icafa827d8e792d4d4d007a9232504965f580b4d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626641Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662951}

R=rbpotter@chromium.org
BUG=964906

Change-Id: I031fd80a4513cc2b99164ad10a10cafd364642b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625848
Commit-Queue: Dan Beam <dbeam@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Auto-Submit: Dan Beam <dbeam@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662950}

  ContextLost_WebGLBlockedAfterJSNavigation
  ContextLost_WebGLUnblockedAfterUserInitiatedReload
  TraceTest_Video_Context_Loss_VP9

These three tests are flaking frequently, and despite two of them
being marked flaky, their failures are showing up often enough in the
data that they're ranked highly on FindIt's flake portal. Skip them
entirely on this configuration.

Bug: 965268
Bug: 965730
Change-Id: Id1b3efe3577d348d0c04fc20a847f9b40a98c046
Tbr: ynovikov@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628391Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662949}

This CL stores per-frame task runners for IPC messages to be executed on
using routing_id. The task runners are stored on IPC::ChannelProxy::Context and will be
looked up each time when IPC messages arrives to the renderer.

Code-wise, this CL
- Introduces IPC::ChannelProxy::Context::{AddListenerTaskRunner, GetTaskRunner}
- {Associate, query} a task runner {to, from} a IPC routing_id
- Before this CL, all IPC tasks were PostTask to {ipc, listener} task runner, but after this CL,
 they are PostTask to the task runner associated to their IPC message's routing_id.
- Renames kInternalNavigation to kInternalNavigationAssociated,
- Associate frame routing_id to per-frame task runner, so the frame IPC messages are routed to
 the task runner.

Design-doc: https://docs.google.com/document/d/1dfQEPeeqOBigyzaeLR5dYaAgeeNDhCkWsPyxodD5xTA/edit?usp=sharing

Change-Id: Ie7500355ca489ee192f9de53f05d07774cf286fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1526067
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662948}

This reverts commit 4ded38ed.

Reason for revert: WebViewPluginTest.TestLoadPluginInternalResource timing out on linux-chromeos-dbg

e.g. https://ci.chromium.org/p/chromium/builders/ci/linux-chromeos-dbg/12542

Original change's description:
> [ MimeHandlerView ] Block PluginStatus != kAllowed/kPlayImportantContent
> 
> Currently, a MimeHandlerView is created as long as there is a plugin
> for it. This behavior undermines issues such as <webview> permissions
> API.
> 
> This CL will avoid creating MimeHandlerView if the plugin is not
> allowed. This change will also make the test
> WebViewPluginTest.TestLoadPluginInternalResource pass with the flag
> MimeHandlerViewInCrossProcessFrame.
> 
> Note that when the plugin is not allowed, no (frame-based)
> MimeHandlerView will be created and the code will follow the ordinary
> CreatePlugin code path.
> 
> Bug: 963694
> Change-Id: I91b88956480139ffdb0df06077d099746b713751
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1622890
> Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
> Reviewed-by: James MacLean <wjmaclean@chromium.org>
> Reviewed-by: Tommy Li <tommycli@chromium.org>
> Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#662641}

TBR=thestig@chromium.org,tommycli@chromium.org,ekaramad@chromium.org,lukasza@chromium.org,wjmaclean@chromium.org

Change-Id: I348e495fd03a3acaed1aaa86d71fee38770a9aa5
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 963694
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627837Reviewed-by: Timothy Loh <timloh@chromium.org>
Commit-Queue: Timothy Loh <timloh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662947}

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

Change-Id: I975346fbb6eb8c6765eb4ad12b7e582b3cc55585
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628003Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662946}

This reverts commit 6eb61402.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 662924 as the
culprit for failures in the build cycles as shown on:
https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzZlYjYxNDAyYzFiMWI0MzAxNzYyYzZhYWFlYTI4YjI5MjFjYmY0YzIM

Sample Failed Build: https://ci.chromium.org/buildbot/chromium/mac-archive-rel/136

Sample Failed Step: compile

Original change's description:
> Removes ui/platform_window/mojo as it is not used by anyone.
> 
> This is to remove the ref to some types under ui/base/ime/mojo, which will be removed later.
> 
> Bug: 965908
> Change-Id: I7979524066104c829b4f4e287a0ab87c9365f124
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626055
> Reviewed-by: Dominick Ng <dominickn@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Commit-Queue: Shu Chen <shuchen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#662924}


Change-Id: I529c9c9f28c32d2799af6a9c7d8a95d6606755ff
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 965908
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628221
Cr-Commit-Position: refs/heads/master@{#662945}

It doesn't seem to have point.

Bug: None
Change-Id: I5e8131578c1191be9f0c27a5196425669470319c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626920
Commit-Queue: Sang Woo Ko <sangwoo108@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662944}

MainMenu.xib primarily consisted of unusable menu items. This CL pulls out the
essentials, and drops support for the rest.

This CL intentionally keeps the logic simple with no additional abstraction
layers. While it would be reasonably simple to reuse chrome's
main_menu_builder.h or to pull out common functionality into builder functions,
the actual lines of code saved would be small and I'd like to avoid unnecessary
abstractions.

Change-Id: I3de68bd6fe3e064b7f83b038688cfbaf0bc4e9e1
Bug: 965663
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627242Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Auto-Submit: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662943}

Bug: 966636
Change-Id: I74b428b24b3ea76d3ed9150c25b34d458652e5c4
Tbr: crouleau@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628236Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662942}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/d390b317dcf7..a541b28d4eba


git log d390b317dcf7..a541b28d4eba --date=short --no-merges --format='%ad %ae %s'
2019-05-24 bpastene@chromium.org Add 'X in tuple()' support to gclient conditionals.


Created with:
  gclient setdep -r src/third_party/depot_tools@a541b28d4eba

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



BUG=chromium:947531
TBR=agable@chromium.org

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

https://swiftshader.googlesource.com/SwiftShader.git/+log/48c8a180b599..8a2441d37d80


git log 48c8a180b599..8a2441d37d80 --date=short --no-merges --format='%ad %ae %s'
2019-05-24 bclayton@google.com vkCmdUpdateBuffer: Make a copy of the data.
2019-05-24 chrisforbes@google.com Fix OpAtomicUMin, OpAtomicUMax
2019-05-24 chrisforbes@google.com Substitute integer 1 for missing 4th component of integer vertex attribute
2019-05-23 bclayton@google.com VkPipeline: Fix unsigned integer underflows in computePrimitiveCount()
2019-05-23 bclayton@google.com VulkanUnitTests: Free / Destroy all Vulkan objects.
2019-05-23 bclayton@google.com ComputeProgram: Don't hold on to the SpirvRoutine.


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

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/133127573,chromium:b/118619338,chromium:b/118383648,chromium:b/133399620,chromium:b/133127573
TBR=swiftshader-team+autoroll@google.com

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

These were all variations of the same issue, so just fix them rather
than do the suppression + fix dance. EmbeddedTestServer callbacks run on
a background thread, so shared state needs to be synchronized.

Bug: 966370
Change-Id: I84dcd747ffaf5d66c09a1b7e10d6bca5ac148231
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626180
Commit-Queue: David Benjamin <davidben@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662939}

Tested in Nexus 5X and iPhone X.

Bug: 925072
Change-Id: I8172fd7ac30f9e1a9466b41f196fd2a92f449546
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1584933
Commit-Queue: Ce Chen <cch@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662938}

This CL splits the interface to two parts so that WebRequestProxyingWebSocket or
extensions proxy only handshake of WebSocket:

interface WebSocketHandshakeClient {
  OnStartOpeningHandshake(WebSocketHandshakeRequest request);
  OnFinishOpeningHandshake(WebSocketHandshakeResponse response);
  OnAddChannelResponse(string selected_protocol, string extensions);
};

interface WebSocketClient {
  OnDataFrame(bool fin, WebSocketMessageType type, array<uint8> data);
  OnFlowControl(int64 quota);
  OnDropChannel(bool was_clean, uint16 code, string reason);
  OnClosingHandshake();
  OnFailChannel(string reason);
};

Performance gain of receive-arraybuffer-1MBx100.html:
Mine: 1050 ms
ToT : 1221 ms

Bug: 865001, 942989
Change-Id: Ia364afd96005a77b1dadf2c95896be5a12827f13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599819Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662937}

Bug: 965395
Change-Id: Ia183ca2e01733612f1228f1905450bfb980ffd6a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627380Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Esmael El-Moslimany <aee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662936}

2 small fixes for OriginTrialContext:
* only exit early from InitializePendingFeatures if there are
  no enabled features, and no navigation features
* ensure OriginTrialContext::IsFeatureEnabled (which is invoked
  via RuntimeEnabledFeatures, for OT features) returns true if
  a feature was activated via navigation.

These were discovered while writing tests as part of
https://chromium-review.googlesource.com/c/chromium/src/+/1601980.


Change-Id: Ia8e711ab61dc4bf14a6e3c12a52faf5e1f096bec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1618175Reviewed-by: Ian Clelland <iclelland@chromium.org>
Commit-Queue: Bryan McQuade <bmcquade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662935}

Fixes nits from thestig@ and compilation failure on Windows. PS#1 is the
original change, later PSs are with the fixes.

------------------------------
These raw files were large and are slowing down the fuzzer process;
this saves 13,416,948 bytes. I've confirmed via MD5 hashes that
the decode path and the yuv path generate the same output data.

BUG=960139
TEST=verify MD5 hashes between compressed and uncompressed variables.
TBR=hiroh,inferno

Change-Id: I32ca1c3162c7bbffcc334b98491bad60ed0b25fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1606595Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: David Staessens <dstaessens@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662934}

Bug: none
Change-Id: Iff7d64dd0ede989f260622c9249983530f55deb8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1622483Reviewed-by: Albert J. Wong <ajwong@chromium.org>
Commit-Queue: Chris Palmer <palmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662933}

It stopped being used in
https://chromium-review.googlesource.com/c/chromium/src/+/1570826 but
the declaration in the header file was never removed.

Bug: 953649
Change-Id: I84d709a33ee7f2eb437ee8235958e8f3962e9c02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627244
Auto-Submit: Patrick Monette <pmonette@chromium.org>
Commit-Queue: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662932}

This will help us better understand the perf difference between users
who encounter pages with OOPIFs and users who don't.

Bug: 946575
Change-Id: I021d1759f0c3c5b0863b9230d5f8d8aacad47e2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625842
Auto-Submit: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662931}

This reverts commit b664d732.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 662925 as the
culprit for failures in the build cycles as shown on:
https://analysis.chromium.org/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2I2NjRkNzMyNjQ1Mjc4NmIzMTY4ZjM0ZDIxY2UyNGNiZDMwNjVkYzYM

Sample Failed Build: https://ci.chromium.org/buildbot/chromium/linux-archive-rel/623

Sample Failed Step: compile

Original change's description:
> Remove ime.mojom and the code on the client side for Mojo-based IMF.
> 
> Bug: 965908
> Change-Id: I83aec36d10247ef7dd08ef58a04f0f2362a8d495
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626053
> Reviewed-by: Dominick Ng <dominickn@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Commit-Queue: Shu Chen <shuchen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#662925}


Change-Id: I3805d9ef6da85e60c980f78bf36b3a9a2353548a
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 965908
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628312
Cr-Commit-Position: refs/heads/master@{#662930}

This reverts commit 8afc180c.

Reason for revert: broke build on GPU FYI Win x64 debug builder:
https://ci.chromium.org/p/chromium/builders/ci/GPU%20FYI%20Win%20x64%20Builder%20(dbg)/13152?blamelist=1#blamelist-tab

Original change's description:
> Add scaffolding for structured GPU command buffer fuzzer
> 
> This CL contains a basic fuzzer for WebGL shaders that shows some
> essential design ideas:
> 
> 1) a protobuf spec defines how shaders will be generated
> 2) conversion from protobuf message to shader string is
>    provided in its own library that has unit tests
> 3) we add a basic fuzzer to compile shader programs using libANGLE
> 
> This is by no means complete and serves as a foundation for the fuzzer
> so subsequent CLs will be easier to review. Later CLs will slowly complete
> the core grammar for GLSL before incorporating some more complex testcases
> from the Khronos compliance suite.
> 
> BUG=900487
> 
> Change-Id: I67df52a73926d22637afad9a966790f34011175c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1623556
> Commit-Queue: Ned Williamson <nedwill@google.com>
> Reviewed-by: Peter Kasting <pkasting@chromium.org>
> Reviewed-by: Kenneth Russell <kbr@chromium.org>
> Reviewed-by: Antoine Labour <piman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#662832}

TBR=pkasting@chromium.org,kbr@chromium.org,piman@chromium.org,xyzzyz@chromium.org,nedwill@google.com

Change-Id: I91debbc67cebc46ecdcaa06b6b1cf587fae781f1
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 900487
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627825Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662929}

https://dawn.googlesource.com/dawn.git/+log/eea209106803..c391fb7c69fd


git log eea209106803..c391fb7c69fd --date=short --no-merges --format='%ad %ae %s'
2019-05-23 enga@chromium.org Use single 64bit atomic refcount for Dawn objects
2019-05-23 shaobo.yan@intel.com Dynamic Buffer Offset : Metal Backend


Created with:
  gclient setdep -r src/third_party/dawn@c391fb7c69fd

The AutoRoll server is located here: https://autoroll.skia.org/r/dawn-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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
TBR=cwallez@google.com

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

https://chromium.googlesource.com/native_client/src/native_client.git/+log/4744a43b6fc4..0ddc03340688


git log 4744a43b6fc4..0ddc03340688 --date=short --no-merges --format='%ad %ae %s'
2019-05-23 thomasanderson@chromium.org Remove non-source sources from binary targets


Created with:
  gclient setdep -r src/native_client@0ddc03340688

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



BUG=chromium:964411
TBR=mseaborn@chromium.org

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

During ForceClose, a closing connection could cause the active request
to 'complete', triggering the rest of the requests to execute. Since
the connections are cleared after-the-fact in ForceClose(), this caused
a UAF.

Instead having specialized weakptr factories here, this change creates
a |force_closing_| variable which is set in ForceClose(), which is used
to ensure reentry doesn't occur.

R: pwnall@chromium.org
Bug: 966557
Change-Id: Iaaf678853431c35299dc9289b505fdf66c19a88e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627707
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662926}

Bug: 965908
Change-Id: I83aec36d10247ef7dd08ef58a04f0f2362a8d495
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626053Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Shu Chen <shuchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#662925}