GitLab

Network traffic annotation is added to
CastChannelSendFunction::AsyncWorkStart().

Bug: 656607
Change-Id: I586c029890d07d922f159db10fbec27bc4d549b4
Reviewed-on: https://chromium-review.googlesource.com/911388
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536671}

Simplify Document::CreateElement by CreateRawElement().

In theory, this CL might have performance change due to code
ordering change; i.e. Built-in elements creation gets slower
slightly, and autonomous custom elements creation gets faster
slightly.  However, this CL doesn't affect Speedometer, which
uses this code path, with my local testing.

Bug: 806641
Change-Id: I623c66cb78b665741a3b93eff1056a671836cb0d
Reviewed-on: https://chromium-review.googlesource.com/918221Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536670}

This change adds the presentation page origin (www.example.com) to the
route details view for local screen casting. The details view also
shows the page title.

Screenshot:
https://drive.google.com/open?id=1linGuorVH62K9bx83iXTWHBJ8EbEmLRH

Bug: 799265
Change-Id: Ieaeb5feab2b429e9e643df0449b5ee9b082e2512
Reviewed-on: https://chromium-review.googlesource.com/910031
Commit-Queue: Takumi Fujimoto <takumif@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536669}

This reverts commit 98f946db

Reason for revert: Suspected cause of bug 810865.

R=shimazu

Bug: 752394,810685
Change-Id: I204cc0070873fcc48716c39fd59ee03a0669bf5f
TBR: shimazu
Reviewed-on: https://chromium-review.googlesource.com/918142Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536668}

content_shell expects all the renderer process to be killed on when
it's shutting down. This CL calls
RenderProcessHost::DisableKeepaliveRefCount to meet the expectation.

This Cl also contains some bug fixes.

 - Remove a DCHECK in DisableKeepAliveRefCount() as it is not specified
   in the header comment.
 - The possibility where RPH::DisableKeepAliveRefCount is already
   called should be taken into account by ServiceWorkerProcessManager.

Bug: 809944
Change-Id: Ic75e949c29a25e91fc3a386b313931a587e56fc2
Reviewed-on: https://chromium-review.googlesource.com/908149Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536667}

GestureListenerManager should stop receiving gesture ack events
from native if ContentViewCore is in the destroyed state. This CL
disconnects the link between native and Java side of
GestureListenerManagerImpl when that happens.

Bug: 803244, 810179
Change-Id: If414dbd44e008fc3b4196d04c13838bc682d49b7
Reviewed-on: https://chromium-review.googlesource.com/915321Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536666}

Reading a few template file many times make make_core_generated_css_longhand_property_classes step slow.
This patch improves generating step time of make_core_generated_css_longhand_property_classes from 32.477s to 2.190s by caching template.

Bug: 804695
Change-Id: I39f7a117b29a502292f00af51485757c73af3166
Reviewed-on: https://chromium-review.googlesource.com/918322Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@google.com>
Cr-Commit-Position: refs/heads/master@{#536665}

Bug: 788890
Change-Id: Iefb3ca691ec6eb9a50dc0cae46a5cbc3bad480ac
Reviewed-on: https://chromium-review.googlesource.com/917924Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536664}

Since IsForbiddenHeaderName() is needed to be called even in
services/network, this patch moves its implementation from
platform/loader to services/network to be used in network service,
the browser process, and Blink.

DEFINE_THREAD_SAFE_STATIC_LOCAL is not needed outside Blink, and
static local variable can be accessed safely among multiple-threads.

Bug: 803766
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Idbd298e9a9528b26b3c0d906dc246303bc9a576b
Reviewed-on: https://chromium-review.googlesource.com/910131
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536663}

This CL makes SignedExchangeSignatureVerifier actually verify
cryptographic signature embedded as "sig" in "Signature" HTTP response header.
Specifically, this CL implements the Steps 11-12 in
https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html#rfc.section.3.6

Bug: 803774
Change-Id: I50b5c7bb09c2c7b8e4020ebd544123c3ddccf4dc
Reviewed-on: https://chromium-review.googlesource.com/903347
Commit-Queue: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536662}

GURL is still used in storage/browser/quota, content/public/browser and
DOMStorageHostMsg_OpenStorageArea. So there are still Origin<->GURL
conversions on those API boundaries.

Bug: 598424
Change-Id: I9e23ccf7abdbf06b62dcd9b44c4309397ee12d8a
Reviewed-on: https://chromium-review.googlesource.com/910731Reviewed-by: Victor Costan <pwnall@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536661}

Original: a8186d45
Reverted: fe4fcad1

The first CL was reverted due to [ Crash ] entry for some tests, which should be
[ Crash Failure ].

Original description:

Add html/details_summary to virtual/incremental-shadow-dom test suites

I am preparing to make IncrementalShadowDOM runtime flag an experimental flag,
however, some tests in html_details are still failing when the flag is enabled.

To track and fix these surely, add these tests to virtual/incremental-shadow-dom test
suites.

TBR=kochi

Bug: 776656
Change-Id: I3bc527b9b957d76c68d239068a079a280543fe85
Reviewed-on: https://chromium-review.googlesource.com/918141Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536660}

The layout test focuses on selection, and has nothing to do with events.
Hence, this patch moves it to editing/selection/mouse

Change-Id: I2993a1e8c0aa89d0f916964a860c378928cffcd7
Reviewed-on: https://chromium-review.googlesource.com/917702Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536659}

We used to have some inline style map layout tests for a subset of
properties. This patch moves them to WPT using the new test harness.

Fixed some bugs involving properties not given the correct metadata
(e.g. border-style should not take an <image>).

Transform is failing tests because it should compute to as specified
but it's computing to 'none' (will fix this later).

TODO in follow up patches:
- Test list-valued properties properly.
- Add more test examples to <position> and <image>.

Bug: 774887
Change-Id: I93f20a457e2220329b661787c7d557ee28b1f62d
Reviewed-on: https://chromium-review.googlesource.com/917921Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536658}

https://webrtc.googlesource.com/src.git/+log/a881ac0ec9e7..5dbb58602f24

$ git log a881ac0ec..5dbb58602 --date=short --no-merges --format='%ad %ae %s'

Created with:
  roll-dep src/third_party/webrtc


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

Change-Id: I5543a73bee27c7d0d78cebc62acc3d9dd8684d3c
Reviewed-on: https://chromium-review.googlesource.com/918181Reviewed-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@{#536657}

This change adds a default handler in order to reduce code duplication
among similar methods in SmbProviderClient.

Bug: chromium:757625
Change-Id: Iaf01dc185f94fae713ffd5f3ec2494c3f910429f
Reviewed-on: https://chromium-review.googlesource.com/917123Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Allen Vicencio <allenvic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536656}

In order to mimic content::ResourceScheduler, this CL has
ResourceLoadScheduler count the number of throttlable requests instead
of the total number of requests when |frame_scheduler_throttling_state_|
is |kNotThrottled|.

Bug: 785770
Change-Id: I58a6d4e1f7792443d1051030d8705074e536259e
Reviewed-on: https://chromium-review.googlesource.com/915882Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536655}

https://pdfium.googlesource.com/pdfium.git/+log/dab8649b7028..2f68cb53f593

$ git log dab8649b7..2f68cb53f --date=short --no-merges --format='%ad %ae %s'
2018-02-14 rbpotter Pdfium: Allow negative font sizes for PostScript printing

Created with:
  roll-dep src/third_party/pdfium


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.


TBR=dsinclair@chromium.org

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

As part of enabling Client Lo-Fi by default, this CL also enables
replacing Server Lo-Fi placeholders with client-generated placeholders
by default.

Bug: 632867
Change-Id: Ib9aeb5b3867574162823b86197f63baf56f1b996
Reviewed-on: https://chromium-review.googlesource.com/912649
Commit-Queue: Scott Little <sclittle@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536653}

The previous implementation created a regular MessageLoop based thread
and posted a single perpetually running task to it, effectively
blocking this MessageLoop.

With MessageLoop redirection to the Task Scheduler, a flush would
result in a hang as this task would never return.

This change moves that single task into its own ThreadMain and changes
the use of Thread to a non-joinable PlatformThread.

BUG=810804

Change-Id: I364acee59f9dd5d80a9c57ebc9d8158ee5faa9c4
Reviewed-on: https://chromium-review.googlesource.com/911902
Commit-Queue: Robert Liao <robliao@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536652}

System notifications generated using CreateSystemNotification has
SYSTEM_PRIORITY. So we don't need to set SYSTEM_PRIORITY manually.

This CL is a clean-up and doesn't change any behavior.

Test: None
Bug: None
Change-Id: I8be104f87b756b5226f9034c9a31c67015978621
Reviewed-on: https://chromium-review.googlesource.com/906172Reviewed-by: Mitsuru Oshima (In Tokyo) <oshima@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Yoshiki Iguchi <yoshiki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536651}

When serializing a filter on a CompositorFrame, we would fail if the
total size exceeds 8K. Instead compute the size required before
serializing the filter.

Note that there are cases where the PaintOpWriter can not trivially
compute the exact size required, with complex types like PaintRecords.
But those should never be serialized with security constraints imposed
on PaintFilters serialized with CompositorFrames.

R=enne@chromium.org

Bug: 810214
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: I2733e3fc36a0b5d8076cb064e5f8de1fc14e33b3
Reviewed-on: https://chromium-review.googlesource.com/909960
Commit-Queue: Khushal <khushalsagar@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536650}

The logic is unintentionally exposed and this CL fixes that.

Bug: 810466
Change-Id: I46091b1ee1fb787195ca9feb7be939df1c5bc258
Reviewed-on: https://chromium-review.googlesource.com/917361Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Takeshi Yoshino <tyoshino@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536649}

Change-Id: Ide1c1ce104d834e40721c1ed55d95b374f1cebc0
Reviewed-on: https://chromium-review.googlesource.com/916623Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536648}

Bug: None
Change-Id: Ia4e3c7c905a8bfa1efdb2c835c7f07ac25310cf4
Reviewed-on: https://chromium-review.googlesource.com/917925Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org>
Commit-Queue: Yoshiki Iguchi <yoshiki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536647}

https://skia.googlesource.com/skia.git/+log/f802e757646f..6ce969472e2e

$ git log f802e7576..6ce969472 --date=short --no-merges --format='%ad %ae %s'
2018-02-14 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ dc2a7f5e3..c5eeb489a (1 commit)

Created with:
  roll-dep src/third_party/skia


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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=caryclark@chromium.org

Change-Id: I12ffdbfd193b48f26aabdecbee61bac08e9ccbf1
Reviewed-on: https://chromium-review.googlesource.com/917646Reviewed-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@{#536646}

of the ancestor clipping layer.

This regressed when we stopped storing clearing clip caches after
scroll of the root layer. It was an oversight to miss this callsite.

Bug: 811486
Change-Id: Ie7b58304bd1cabfb1cd727bcdf0996d1c91e2e2c
Reviewed-on: https://chromium-review.googlesource.com/916722Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536645}

Blink was failing a DCHECK when it expected a redirect to be taken because
the request mode was 'follow' and the response had a redirect status code
and Location header. However, Chrome's //net considers a Location header
with an empty value to be the same as no Location header at all. See the
comments on bug 810288 about net::HttpResponseHeaders::IsRedirect().

WPT tests are added. The spec is unclear (https://github.com/whatwg/url/issues/373)
but seems to either say to fail with network error or enter a loop of self-redirects
that will eventually hit the redirect limit and fail with network error.
Chrome currently fails this test because it treats the Location as
as non-existent, i.e., not a redirect response.

Bug: 810288,707185
Change-Id: Iaca93976aaa697380b1542ab45d63c318f5050b0
Reviewed-on: https://chromium-review.googlesource.com/910753Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536644}

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

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

Previously, some tests applied to hosted apps, some applied to bookmark
apps, and some were duplicated between the two. Almost all tests apply
equally to both, so we parameterize the test and remove duplicated
logic.

Bug: 811175
Change-Id: I943e2ce49f3a62354121dfd83c3c9028776b8198
Reviewed-on: https://chromium-review.googlesource.com/913188
Commit-Queue: Matt Giuca <mgiuca@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536642}

There is only three common accessors from AccessibleNode and the
bool attributes defined in ax_enums.mojom for boolean types.

BUG=792783

Change-Id: Ifdf438708ce1ea71e36055fd37845004b8a6434d
Reviewed-on: https://chromium-review.googlesource.com/896766
Commit-Queue: Meredith Lane <meredithl@google.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Alice Boxhall <aboxhall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536641}

https://pdfium.googlesource.com/pdfium.git/+log/20eb52e66c56..dab8649b7028

$ git log 20eb52e66..dab8649b7 --date=short --no-merges --format='%ad %ae %s'
2018-02-13 rharrison Change return value of GetAvailInput
2018-02-13 dsinclair Add last_child to CFX_XMLNode
2018-02-13 thestig Remove old version of InitializeV8ForPDFium().
2018-02-13 thestig Teach fixup_pdf_template.py to automatically calculate stream length.
2018-02-13 dsinclair Split CFX_XMLNode::SaveXMLNode apart
2018-02-13 dsinclair Cleanup CFX_XMLNode pointers
2018-02-13 dsinclair Cleanup CFX_XMLDoc::SaveXMLNode

Created with:
  roll-dep src/third_party/pdfium


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.


TBR=dsinclair@chromium.org

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

Inform Ash of the vector icon for a chrome-generated notification by
passing the icon's identifier over mojo. Only a pre-determined list
of vector icons that ash is expecting to see will be accepted.

Change-Id: I0b87cd4d4261c99f63cb95881c51d5c4bb479c7d
Reviewed-on: https://chromium-review.googlesource.com/903143
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536639}

This patch converts the layout tests with selection_test to promote the
usage of W3C testharness, and also as a preparation for implementing
text hit-testing in LayoutNG.

Bug: 679977, 811502
Change-Id: I83ced4c1af102c56471f2083bbc5593b4ee68b43
Reviewed-on: https://chromium-review.googlesource.com/915138
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536638}

This reverts commit a8186d45.

Reason for revert: Test failures, as per
https://uberchromegw.corp.google.com/i/chromium.webkit/builders/WebKit%20Linux%20Trusty/builds/40283

Original change's description:
> Add html/details_summary to virtual/incremental-shadow-dom test suites
> 
> I am preparing to make IncrementalShadowDOM runtime flag an experimental flag,
> however, some tests in html_details are still failing when the flag is enabled.
> 
> To track and fix these surely, add these tests to virtual/incremental-shadow-dom test
> suites.
> 
> Bug: 776656
> Change-Id: Ied9d5ff914fc998a04efac1d944708c313e82b7b
> Reviewed-on: https://chromium-review.googlesource.com/914944
> Reviewed-by: Takayoshi Kochi <kochi@chromium.org>
> Commit-Queue: Hayato Ito <hayato@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#536599}

TBR=kochi@chromium.org,hayato@chromium.org,futhark@chromium.org

Change-Id: Iceaf52b9e359f254b7dd598ab3b0ba38215638c7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 776656
Reviewed-on: https://chromium-review.googlesource.com/917882Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Hayato Ito <hayato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536637}

This CL is basically same as https://chromium-review.googlesource.com/c/chromium/src/+/903942,
but adds fix for use-after-poison.

PresentationAttributeCacheCleaner was introduced before purging memory
was introduced.

This CL removes PresentationAttributeCacheCleaner to clear cache soon
instead of delyaing with timers.

This is part of efforts to replace default timer task runners with
other appropriate task runners in the renderer.

Bug: 624694, 804694
Change-Id: Ief4ab5240f1c93bf2383a7ed3de61391bd616f8c
Reviewed-on: https://chromium-review.googlesource.com/916162Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536636}

alph@ demonstrated that using a Poisson process sampling algorithm provides
highly actionable data with low overhead. This CL adds a flag to do that for OOP
HP.

The sampling algorithm guarantees that large allocations, and frequent, small
allocations are recorded with high fidelity. Infrequent, small allocations will
have noise, but those are precisely the allocations we're not interested in.

The new flags are --memlog-sampling and --memlog-sampling-rate=<XYZ>. The former
flag is available in about://flags with a default sampling rate of 1000.

Bug: 810748
Change-Id: Id88186bdd0c17287a05b44761f6c4d9d9fd2f3cf
Reviewed-on: https://chromium-review.googlesource.com/911891
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Alexei Filippov <alph@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536635}

This upgrades --interactive to a test-launcher-scope switch (necessarily
renaming it to --test-launcher-interactive) and treats it as a timeout
specifier.  For browser UI tests on Windows, this means the parent process will
now get an (effectively) unlimited timeout and not just the child process, so
the test won't terminate early.

BUG=none
TEST=none

Change-Id: I56b02ba30ad0df6617b0f1f95d9986724c5035a0
Reviewed-on: https://chromium-review.googlesource.com/909920
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Trent Apted <tapted@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536634}

BUG=804041

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel
Change-Id: If1e7b249d5103374f6c0129650480cb4b742c880
Reviewed-on: https://chromium-review.googlesource.com/908254Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Xing Xu <xing.xu@intel.com>
Cr-Commit-Position: refs/heads/master@{#536633}

The _breakpointStorageId had line and column swapped

Change-Id: Ieed0cd10ecf5816a62c7822b587778a2b41cd5f3
Reviewed-on: https://chromium-review.googlesource.com/917440Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Joel Einbinder <einbinder@chromium.org>
Cr-Commit-Position: refs/heads/master@{#536632}