GitLab

The PerformanceManager page freezing policy doesn't take into account
the loading state of a tab when emitting freezing signals. As a result
some unloaded tabs can receive a freezing signal and there won't be
another freezing attempt once the tab gets loaded.

This fix this problem by waiting for the tab to transition to the
loaded state before emitting the freezing signal.

Bug: 1168735
Change-Id: I13b92600a2df7fa8bfc592a2711cb33b0631e409
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2641154Reviewed-by: Joe Mason <joenotcharles@chromium.org>
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845415}

Bug: 1125150
Test: browser_tests --gtest_filter=DiagnosticsApp*
Change-Id: I53ad5058338326c796b35d2141f2051d683aa149
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2616742Reviewed-by: Joon Ahn <joonbug@chromium.org>
Reviewed-by: Bailey Berro <baileyberro@chromium.org>
Commit-Queue: Michael Checo <michaelcheco@google.com>
Cr-Commit-Position: refs/heads/master@{#845414}

Adds a new Extra to intents created from the Open In Browser CCT Menu
item so that we can differentiate them from other View intents
received by ChromeTabbedActivity for the purposes of LaunchCauseMetrics

Bug: 1163961
Change-Id: I18550a1b6cf5813771e56f8ae7b7f0a22d4fee3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639301
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845413}

Currently this has no real impact because connection migration isn't enabled in IETF QUIC. But once we start experimentation, an explicit flag check will help us turn on/off the feature.

I'll follow up by adding DCEHCK in QuicConnection.

Bug: 1155306
Change-Id: I1794edb3c528bfa42910d88f394fd024f0f3021f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2641089
Commit-Queue: Renjie Tang <renjietang@chromium.org>
Commit-Queue: David Schinazi <dschinazi@chromium.org>
Auto-Submit: Renjie Tang <renjietang@chromium.org>
Reviewed-by: David Schinazi <dschinazi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845412}

Uses the content suggestions content height to adjust the feed inset and
offset correctly. This revealed that the content suggestions height was
not taking the safe area insets into consideration, so they are now
handled across the refactored NTP.

Also fixes occasional crash when changing between NTPs by ensuring that
the fake omnibox doesn't have multiple parent views/VCs at once.

Bug: 1114792
Change-Id: I458365dc5c494fcc3155cff53e9a368988d83538
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635450
Commit-Queue: Adam Trudeau-Arcaro <adamta@google.com>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845411}

Bug: 1168584
Change-Id: I7eb840feafb2ba0c734713f88d48bcd822004472
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640933
Commit-Queue: Peng Huang <penghuang@chromium.org>
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845410}

Several Picture-in-Picture browser tests require video playback to have
started, but they didn't really enforce it considering that the `play()`
method of the media element is asynchronous. In particular, a test
verifying the visibility of a control bound to a MediaSession action
might never see the control: The control is visible when the video is
actually playing and also it's hidden automatically 2.5 s after the
start of mouse hover. If playback doesn't start during those 2.5 seconds
(which is plausible if the test machines are under heavy load) the
hiding timeout will elapse first.

Bug: 985303
Change-Id: I7f9d62e8496cb5419445dd27c94fde91d541a6ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635156Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: Wojciech Dzierżanowski <wdzierzanowski@opera.com>
Cr-Commit-Position: refs/heads/master@{#845409}

The script had a couple of issues that crop up with
Python3's str/bytes/unicode changes.

Bug: 1168342
Change-Id: Ic1ff68d099245bcf5b39382bc5f3919fd13609a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2638785Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@google.com>
Cr-Commit-Position: refs/heads/master@{#845408}

According to the standard https://html.spec.whatwg.org/multipage/imagebitmap-and-animations.html
when creating a new ImageBitmap that has resizeWidth or resizeHeight
equal to 0, it has to throw an exception.

As in some cases, user can provide value between 0 and 1, these will be
rounded down to zero (as according to the standard those resizeWidth and
resizeHeight is a unsigned long, so it cannot have decimal values).

Bug: 1137216
Change-Id: I4a0b241fa8a94cc6b59c77bb1313f7a4d7983733
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636373Reviewed-by: Aaron Krajeski <aaronhk@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Commit-Queue: Juanmi Huertas <juanmihd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845407}

When resuming from the end of a nodeGroupItem,
findNodeFromNodeGroupByCharIndex returns a node with a -1 offset. This
will throw exceptions. This CL fixes this bug.

Bug: 1167260
Change-Id: I2fe466a07f3daa2103dec53e6ebcedd5be27d285
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2638863
Commit-Queue: Lei Shi <leileilei@google.com>
Reviewed-by: Katie Dektar <katie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845406}

Screenshot: http://screen/6yMAYdeURT7ZxWm

Bug: 1168641
Change-Id: I019bfed56e7e0f4e26fa3d6b9d4a71939a256348
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640637
Commit-Queue: Gavin Williams <gavinwill@chromium.org>
Reviewed-by: Jesse Schettler <jschettler@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845405}

We're no longer blocked on using lottie, see crbug.com/1116501
I was able to confirm a lottie animation works.

Bug: 1158468
Change-Id: I05724d6f24630195e8eed0ec985edcc6792e9337
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2636848Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Commit-Queue: Dan H <harringtond@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845404}

Defaults to the current emoji ordering from emoji-metadata,
but this will allow smaller emoji data files to be used for tests.

Change-Id: Ibc3ffdeb0c05f7ad9c3880c899c92ef6dc6cbcbd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639713Reviewed-by: John Palmer <jopalmer@chromium.org>
Reviewed-by: Keith Lee <keithlee@chromium.org>
Commit-Queue: Kenton Lam <kentonlam@google.com>
Cr-Commit-Position: refs/heads/master@{#845403}

This interface will allow other components to receive the process
metrics gathered by ProcessMonitor.

Bug: 1166820
Change-Id: Ie65de109bb2e596dcd3a9ba343b8f34138041ee8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631245
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845402}

Split skip UserAction, update ExitReason suffixes.

Fixed: 1156172
Change-Id: Ice46677aa47673040029fe72f55807d6841e5fde
Bug: 1156172
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632689
Commit-Queue: Roman Aleksandrov <raleksandrov@google.com>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845401}

This class is test and Chrome OS-only. Move it to
chrome/browser/chromeos/login/test.

The .cc/.h files are also moved to the build target
//chrome/browser/chromeos:test_support, together with some of its
dependencies.

Bug: 1164001
Change-Id: I12331c093a8b1ec42153a07d20dd4397c1ed8d5e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632745
Owners-Override: James Cook <jamescook@chromium.org>
Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845400}

This CL ensures MV tile icon to be updated when a new icon is fetched.
Besides, a test is added for the correctness of MV tiles order.

Bug: 1166238
Change-Id: Ic6d7157c6f03d24b02d38171f0727bf2b6a56463
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627748Reviewed-by: Xi Han <hanxi@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Commit-Queue: Hao Dong <spdonghao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845399}

When Forced Colors happened at computed value time, caret-color would
pick up the forced color through currentcolor. However, now that
we are forcing colors at used value time, it appeared that caret-color
regressed since it no longer picks up the forced currentcolor.

This change adds caret-color to the properties that are adjusted in
Forced Colors Mode, and forces it to use the forced currentcolor.

I've opened a new spec issue to address this, as well as a few other
color properties that I noticed would also be affected by this:
https://github.com/w3c/csswg-drafts/issues/5873

Bug: 1166392
Change-Id: I239700441ed17bfd0b33443887a0c72793843cf1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627779Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#845398}

Span attribute means that COL/COLGROUP span multiple columns.
Old code incorrectly defined background geometry separately
for each column.
This happened because I just ported handling of "width".
width attribute applies to each column within COL/COLGROUP.

New behavior is intuitive, and matches FF.

Change-Id: Ibdd397825ed363de2695f4ff43dd8dd4df065357
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633438
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845397}

It appears that dead shared and/or dedicated worker clients of
a shared worker may have outstanding client registrations as the
service worker starts.

Bug: 1168113
Change-Id: Ie19f3fb90c9252502a29eadfa1bec52acd6e5f64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2637256
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Reviewed-by: Patrick Monette <pmonette@chromium.org>
Auto-Submit: Sigurður Ásgeirsson <siggi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845396}

https://webrtc.googlesource.com/src.git/+log/812c73cdc25a..0be184647794

2021-01-20 danilchap@webrtc.org Fix enabling DependencyDescriptor for VP9 with spatial layers
2021-01-20 brandtr@webrtc.org Add `.cache` to .gitignore.
2021-01-20 danilchap@webrtc.org Cleanup FakeRtcEventLog from thread awareness

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: None
Tbr: webrtc-chromium-sheriffs-robots@google.com
Change-Id: I77eefe3f5ed2bc58e611f69a034c24b4c3e19b79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640889Reviewed-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@{#845395}

Fixed: 1167843
Change-Id: Ic4f3a5bcd88ea036a6ec82ddc91d0946622c7968
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639654Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845394}

The RG16_EXT format was added to resource_format.h, but not added here.
This is causing mojo validation errors with P010 surface because they
are outside the allowed enum range.

BUG=b:178022921
TEST=Mojo validation error is gone

Change-Id: Ia8e5d9fa433e5bcfc30550fbd10a6e929a5199bf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639219
Auto-Submit: Jeffrey Kardatzke <jkardatzke@google.com>
Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Commit-Queue: Jeffrey Kardatzke <jkardatzke@google.com>
Cr-Commit-Position: refs/heads/master@{#845393}

for testing. This was requested by Patricia.

BUG=none
TEST=none

Change-Id: I88c61ae43d02a611efbfc868861a10250144b838
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640813Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845392}

Bug: 1167768
Change-Id: I3d237173fca7658d9e4ad9c88b51e4a899efd4ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2637726
Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Auto-Submit: Andres Calderon Jaramillo <andrescj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845391}

These were fixed for standalone PDFium at
  https://pdfium-review.googlesource.com/c/pdfium/+/73015

but still persist in Chromium's version of /.gn

Change-Id: I57fa0250a5a668935978988d949311d86f9bc244
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640922Reviewed-by: Erik Staab <estaab@chromium.org>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845390}

This CL makes it possible to further extract web_contents from
the base classes of PasswordProtectionService and
PasswordProtectionRequest which will be moved to /core.

The content or ios derived class implementations of
ShowModalWarning can extract WebContents or WebState respectively
from the request object.

Bug: 1147967
Change-Id: I1f2d4b580a2dc83b5ae23db6a79db59bf8303d91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633968Reviewed-by: Bettina Dea <bdea@chromium.org>
Reviewed-by: Adrienne Porter Felt <felt@chromium.org>
Reviewed-by: Ali Juma <ajuma@chromium.org>
Commit-Queue: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845389}

- This CL adds a sub label to cellular networks which have not yet been
  activated to indicate the user can click and activate that network.
- Opens new cellular setup dialog when "click to activate" is clicked

Screenshot: https://screenshot.googleplex.com/3hmXeFo7gPQhcBZ.png

Bug: 1093185
Change-Id: I5f7df05123be56e97c74125313263ff50d0a0124
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2629989
Commit-Queue: Nnamdi Theodore Johnson-kanu <tjohnsonkanu@google.com>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Azeem Arshad <azeemarshad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845388}

To help track down the cause of excess dxva usage from D3D11, this CL
adds a sparse histogram of media::StatusCodes that are returned from
D3D11VideoDecoder and the H264 / VP9 accelerators.

Bug: 1168304
Change-Id: If2c3c1990cf50776c69958048b7b9c2969095c3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2638247
Commit-Queue: Frank Liberato <liberato@chromium.org>
Reviewed-by: Ted Meyer <tmathmeyer@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845387}

Bug: 1164001
Change-Id: Ic4018a71196b0c6e0e9f616873aacaf826155cbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640055Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com>
Cr-Commit-Position: refs/heads/master@{#845386}

Also updating histograms in other/ to use my @google.com address, as that's what I use for code reviews.

Bug: 1165257
Change-Id: Ic097d36841e66127859967fb2e844185079a1dad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631331
Commit-Queue: Josh Simmons <jds@google.com>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845385}

This corrects two issues with suspend:
* Ambient mode does not restart when waking up from suspend
* Flash of old Ambient mode photo displays when opening lid from suspend

Block Ambient mode from restarting after |SuspendImminent| until
|SuspendDone| is received. Upon |SuspendDone|, also restart Ambient mode
lock screen timeout if appropriate.

Start Ambient mode, close lid while active. Reopen lid, wait 7 seconds,
Ambient mode starts again over lock screen.

BUG=b:177325727
BUG=b:177692036
TEST=ash_unittest --gtest_filter="AmbientControllerTest.*Suspend"

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Change-Id: I8d52af80ab7dd49538998d0e8831ee3c10d2919a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625727
Commit-Queue: Jeffrey Young <cowmoo@chromium.org>
Reviewed-by: Tao Wu <wutao@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845384}

This change rearranges the steps of the SortAndCull to ensure the
Matches with Headers are only grouped and demoted after the
GroupBySearchVsURL completes.

This update prevents the GroupBySearchVsURL from pushing the URLs
below the search suggestions, including the matches with group
headers.

Bug: 1165941
Change-Id: I70ea0815ab2c2c8b652368819c2eef1c40f692ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626188Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Tomasz Wiszkowski <ender@google.com>
Cr-Commit-Position: refs/heads/master@{#845383}

See https://bugs.chromium.org/p/chromium/issues/detail?id=1167463#c7 for
screenshots of change. The total vertical space saving is 36px.

Bug: 1167463
Change-Id: I82eb57e7a56202024b9fc1ed31ca2b3d2292fa21
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2637186
Commit-Queue: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845382}

Makes the middle slot promo Finch-configurable. Flag is enabled by
default.

Bug: 1166869
Change-Id: If6d4e06577f99b635f04fbe406334b66f62210b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2638934
Commit-Queue: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845381}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/40fbf5738639..80d2a97665e9

2021-01-20 tmathmeyer@chromium.org Hide overflow caused by excessively long urls.

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Bug: chromium:1129296
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: I722855faa917d419713201a5dc7268b26709a844
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640886Reviewed-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@{#845380}

This CL adds a feature flag and a common interface for the different
Contextual Search panel implementations.

Binary-Size: Increase is temporary while we experiment with refactoring
Bug: 1147611
Change-Id: I7c0b264846c5a19c61a9830222f21525daf42b12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2638777
Commit-Queue: Sinan Sahin <sinansahin@google.com>
Reviewed-by: Donn Denman <donnd@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845379}

On Android we create the renderer main thread from Java instead of using
the process's actual main thread (which is functioning as the Android
looper). This means that rather than the stack size being determined by
the kernel's defaults, it's determined by the JVM's defaults, which are
considerably smaller, and we overflow the stack in rare cases that work
on other platforms.

Use the stackSize parameter to the Java Thread constructor to request a
larger stack: 4MB in 32-bit processes and 8MB in 64-bit processes (to
match crrev.com/c/2490667 which set this for Windows). This parameter is
not required to be honoured by the JVM but ART on Android does use this
as a lower bound on the thread's stack size on all the Android versions
we care about.

Verified that this works by inspection of /proc/$pid/maps on ToT
Android, which gives names to the thread stack mappings that include the
tid (earlier versions of Android do not do this and there's no easy way
to tell how big non-main-thread stacks are).

Fixed: 1151869
Change-Id: I42e0bd987abc4f57a65e1c25436568eb51d8ac02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625887
Auto-Submit: Richard Coles <torne@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845378}

https://android.googlesource.com/platform/external/perfetto.git/+log/a3c06205b28b..477bd92472cc

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium
Please CC perfetto-bugs@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

Tbr: perfetto-bugs@google.com
Change-Id: I91669c7eb0ffb88696494a31b93471bc689f96f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639164Reviewed-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@{#845377}

Add blink::ContainerNode::hasChildren() to shadow
blink::Node::hasChildren() to avoid the virtual dispatch that leads to
at least 7-12% regressions in some blink query-selector benchmarks, when
we know the type statically to be ContainerNode. This is especially
bad on Android, where the blink::Node::hasChildren() function is big
enough not be inlined, so we miss out on extra optimizations.

See the linked bug for a more in-depth analysis of the regression.

Bug: 1149340
Change-Id: Ida1d8b609b23ada25ae5ed67826439c74633721c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633194Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Matthew Denton <mpdenton@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845376}