This CL tentatively fixes an issue where an RTCDataChannel can be closed
due to an error, but it crashes if the RTCError doesn't have any error
details set. This results in a NOTREACHED being hit when creating the
RTCErrorEvent.

While this CL fixes the crash, there might be underlying issues that
need to be addressed further.

(cherry picked from commit 1116bad3)

Fixed: 373898146
Change-Id: I06027cc666d709ae3eee72832508bf6283ab3954
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5937135


Reviewed-by: Florent Castelli <orphis@chromium.org>
Auto-Submit: Thomas Guilbert <tguilbert@chromium.org>
Commit-Queue: Florent Castelli <orphis@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1370595}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5961157


Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/branch-heads/6778@{#797}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Mac Arm PGO profile from chrome-mac-arm-6778-1729792496-74b0aea507a4dda7ca0a940514997855353b448c-7e1b3bdb.profdata to chrome-mac-arm-6778-1729799348-21b26356c77908a3a1112dc6d7a946dfb3597976-3dede127.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: I5461143908e10c2ab60c2ddeb959f38dcd90a81e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962664
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#796}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729792089-93441a4cb57d28426b950d2f3e169a933cb4f4ba-b13d0f25.profdata to chrome-android64-6778-1729793795-9e092d1de06ffe81889dff2cbbaf69eaf09214b9-6842d3d8.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: If0d54542e853843842928e8c8269894e7937fb35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962988
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#795}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

(cherry picked from commit 158c63f1)

Bug: 375067118, b:359912571
Change-Id: Ie61f3dca951ed43cc8ddd3e08c194ae379a17b95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5952842


Reviewed-by: Jason Hu <hujasonx@google.com>
Commit-Queue: Bryan Nguyen <nguyenbryan@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1372306}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962363
Auto-Submit: Bryan Nguyen <nguyenbryan@google.com>
Commit-Queue: Jason Hu <hujasonx@google.com>
Cr-Commit-Position: refs/branch-heads/6778@{#794}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Linux PGO profile from chrome-linux-6778-1729770119-b8ff6b2a0122607d90160145115a928733baf7f7-17356080.profdata to chrome-linux-6778-1729792496-88a20c965f8dd3069f31b807267968ccb5f0dc47-7e1b3bdb.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m131.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I8f9ccf6d950755b10089eed5b642709923cb64d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5963002
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#793}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

(cherry picked from commit 80b19165)

Bug: 374132193
Change-Id: I49965feb89a0601164e01343cda37737f289d1de
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5940371


Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Reviewed-by: Orin Jaworski <orinj@chromium.org>
Reviewed-by: Roman Arora <romanarora@chromium.org>
Commit-Queue: Orin Jaworski <orinj@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1370286}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962617
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#792}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

(cherry picked from commit 622b01b4)

Dump without crashes can be noisy in stable. This flag will enable us to
turn it off and on in different versions of Chrome avoiding extra noises
while being informed about them happening.


Bug: 374365779, 373617224, 375170577
Change-Id: Iee0536c303a571f962b1816667d2fbc67da8ff46
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5950247


Reviewed-by: William Liu <liuwilliam@chromium.org>
Reviewed-by: Khushal Sagar <khushalsagar@chromium.org>
Commit-Queue: Baran Erfani <baranerf@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1372216}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5953097
Cr-Commit-Position: refs/branch-heads/6778@{#791}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

(cherry picked from commit 9b8090c0)

Bug: 365549194
Change-Id: I8c3bedcc3dec82b387f31fc67a89bdf6031f6ccb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5953614


Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Ali Juma <ajuma@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1372093}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5961772
Auto-Submit: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Ali Juma <ajuma@chromium.org>
Cr-Commit-Position: refs/branch-heads/6778@{#790}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Mac Arm PGO profile from chrome-mac-arm-6778-1729784387-8eb1d7720591a524ea1fb318d6d3aa9c079b01ea-95bb3806.profdata to chrome-mac-arm-6778-1729792496-74b0aea507a4dda7ca0a940514997855353b448c-7e1b3bdb.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: I76195474c0bd7767455367097020edd618e75f61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962555
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#789}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

This reverts commit 7a0215d1.

Reason for revert: Revert for weeks 3 and 4 of beta.  See
go/partition-alloc-rollout-v4 for details.

Original change's description:
> ios: Enable PA-E checks for metadata corruption issue investigation
>
> Bug: 371135823
> Change-Id: Ia2d5ed7a9f466be89af144f5f07239151bf05bb8
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5925134


> Commit-Queue: Rohit Rao <rohitrao@chromium.org>
> Auto-Submit: Justin Cohen <justincohen@chromium.org>
> Reviewed-by: Rohit Rao <rohitrao@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1367514}

(cherry picked from commit 682f0aca)

Bug: 371135823
Change-Id: I0f1aa4144a5c945b407579416b5b855a601b0727
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962418


Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Justin Cohen <justincohen@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1373384}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962480


Commit-Queue: Harry Souders <harrysouders@google.com>
Reviewed-by: Harry Souders <harrysouders@google.com>
Owners-Override: Harry Souders <harrysouders@google.com>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/branch-heads/6778@{#788}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

(cherry picked from commit ab7d0521)

Bug: 372535307
Change-Id: I3c8ff10d896e309c34b997d3d22793ccbd5fbf1b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5950645


Commit-Queue: Steven Holte <holte@chromium.org>
Reviewed-by: Jun Zou <junzou@chromium.org>
Auto-Submit: Steven Holte <holte@chromium.org>
Reviewed-by: Zekun Jiang <zekunjiang@google.com>
Reviewed-by: Orin Jaworski <orinj@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1372250}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5960798
Commit-Queue: Zekun Jiang <zekunjiang@google.com>
Auto-Submit: Zekun Jiang <zekunjiang@google.com>
Cr-Commit-Position: refs/branch-heads/6778@{#787}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Change-Id: I7e8f07c59583095df4ee4eef4a22628fae7d45b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5961159
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/branch-heads/6778@{#786}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

(cherry picked from commit 0e8f81e4)

Bug: 375051688, 375238441
Change-Id: Ie684b68feb6ee0dc89cc34d3230bf1089720fc2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5955570


Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Auto-Submit: Khushal Sagar <khushalsagar@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1372487}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5961985


Commit-Queue: Khushal Sagar <khushalsagar@chromium.org>
Reviewed-by: William Liu <liuwilliam@chromium.org>
Commit-Queue: William Liu <liuwilliam@chromium.org>
Cr-Commit-Position: refs/branch-heads/6778@{#785}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729789369-f423b3acca3494dd1252f49f5f3d0437e25e533f-a9ac806d.profdata to chrome-android64-6778-1729792089-93441a4cb57d28426b950d2f3e169a933cb4f4ba-b13d0f25.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: Id0256ebfe28834ce9aad2d8c6911a212e04fe4ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5963098
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#784}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729786993-08ec7f60a4b9a49fc12d4a570af1a213366b040b-cd03a389.profdata to chrome-android64-6778-1729789369-f423b3acca3494dd1252f49f5f3d0437e25e533f-a9ac806d.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: I33203e0aeb132f73c9966f1abbcead3a215a5cd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962544
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#783}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

We failed to update scrolling_contents_cull_rect on the cc scroll tree
if a scroll only caused repaint but not a full PaintArtifactCompositor
update. The wrong cull rect caused false paint checkerboarding.

Now update scrolling_contents_cull_rect on the cc scroll tree during
PaintChunksToCcLayer::UpdateLayerProperties() to ensure it is updated
for both full and repaint-only updates.

(cherry picked from commit 633b1b17)

Bug: 373664061
Change-Id: Ibbc153e256f5f6c64c6003ad8e3a820eff60882a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5940118


Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1372212}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962359
Auto-Submit: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#782}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

This is a reland of commit 69eb90b5
with a fix for the test failure, which is to move the setting
of drag_drop_in_progress_ so that it's set for both the touch
and non-touch case.

Original change's description:
> win: tweaks to touch drag.
>
> Verify that mouse cursor is in the drag source window.
>
> Tested manually.
>
> Low-Coverage-Reason: HARD_TO_TEST
> Bug: 40312079, 370856871
> Change-Id: I800e915f566d63354e4e1d1e1f7edd79200f7553
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5927282


> Reviewed-by: Scott Violet <sky@chromium.org>
> Commit-Queue: David Bienvenu <davidbienvenu@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1370869}

(cherry picked from commit 5398c8d0)

Low-Coverage-Reason: HARD_TO_TEST
Bug: 40312079, 370856871, 374385590
Change-Id: I387757524615c3b3fe4dd6865825331db5bee44e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5943487


Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: David Bienvenu <davidbienvenu@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1371525}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5952499


Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: David Bienvenu <davidbienvenu@google.com>
Cr-Commit-Position: refs/branch-heads/6778@{#781}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Win64 PGO profile from chrome-win64-6778-1729749474-482894a5b92558a41d315a49d46ca407d83dc5d8-a526e8e9.profdata to chrome-win64-6778-1729770119-25abc6940865ae73da94c28d64f9e8113f68abc7-17356080.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m131.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I95169951ae30050dc574c39b296db71e45921511
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962022
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#780}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Automatic update for 2024-10-24 UTC

Change-Id: I814602b9e533217921446243c0138c7602897386
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5961742
Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Cr-Commit-Position: refs/branch-heads/6778@{#779}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729784387-3f0c2fb931ee79cfb9631e1112234101a25e9f64-95bb3806.profdata to chrome-android64-6778-1729786993-08ec7f60a4b9a49fc12d4a570af1a213366b040b-cd03a389.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: If537dc53d65d178d25881f19ee3ebba173ef88a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5960560
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#778}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Mac Arm PGO profile from chrome-mac-arm-6778-1729777904-2cd01c1a9119763c5b857b43b09eb3aaa3400060-888c86be.profdata to chrome-mac-arm-6778-1729784387-8eb1d7720591a524ea1fb318d6d3aa9c079b01ea-95bb3806.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: Id84792aa04a250d686dfa9d71c2a7f44368eaa56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962567
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#777}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729782015-1271a7e8a0aa375de43bc8bc84e1df6bca41f55c-e30e5756.profdata to chrome-android64-6778-1729784387-3f0c2fb931ee79cfb9631e1112234101a25e9f64-95bb3806.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: If8a9e86022f83b767ae98ea3bc9b3fd9eea62e42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962566
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#776}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

(cherry picked from commit 0c1e4f88)

Bug: 374360783
Change-Id: I86dee74a62b32d934c2e58290c79e3239bfcbf13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5943582


Auto-Submit: Robbie Gibson <rkgibson@google.com>
Commit-Queue: Guillaume Jenkins <gujen@google.com>
Reviewed-by: Gayane Petrosyan <gayane@google.com>
Commit-Queue: Gayane Petrosyan <gayane@google.com>
Reviewed-by: Guillaume Jenkins <gujen@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1371519}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5958770


Commit-Queue: Robbie Gibson <rkgibson@google.com>
Reviewed-by: Paul Adedeji <pauladedeji@google.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#775}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Make DynamicSafeAreaInsets a web settings, and let the browser decide
if the feature should be turned on based on activity configurations.
This CL limits the feature to users that are eligible for edge to edge
for Chrome on Android.

Context: When Chrome draws edge to edge, the tab content area will draw
into the bottom notch. This feature is targeting phones with Android R+
and using the gesture navigation mode.

(cherry picked from commit 072611d7)

Fixed: 375244094
Bug: 374387520
Change-Id: Id53a88e9d6e9c3565fe53aaaebe0f6bb174b2c89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5943708


Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Charles Hager <clhager@google.com>
Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Reviewed-by: Theresa Sullivan <twellington@chromium.org>
Commit-Queue: Wenyu Fu <wenyufu@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1372441}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5959335
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#774}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Win32 PGO profile from chrome-win32-6778-1729749474-43b3c9ed96574980e223b14c144a31de904292e1-a526e8e9.profdata to chrome-win32-6778-1729770119-9bb2408421758b751249c6330205b936845d4b9b-17356080.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m131.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I5c35b55e316dc86c5d12fc4a3125f3c8a6be5c71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962021
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#773}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729779039-9928a8b36dd84cc3368770d194731d1d02a39131-dc5a9be3.profdata to chrome-android64-6778-1729782015-1271a7e8a0aa375de43bc8bc84e1df6bca41f55c-e30e5756.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: I91cda3943358144e377b3bc3525738fbf950ef5c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962207
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#772}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Automatic update for 2024-10-24 UTC

Change-Id: Ia2017a7695f80917b49ba20b094ffd9fc1f1b5bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962459
Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Cr-Commit-Position: refs/branch-heads/6778@{#771}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729776239-0e2175d43508a0701fee1dfe6df8d6df29710b80-a2dfde63.profdata to chrome-android64-6778-1729779039-9928a8b36dd84cc3368770d194731d1d02a39131-dc5a9be3.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic4c71fc6648faf813e1d8dd643d204a52043c339
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962556
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#770}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

GetNavigationEntryScreenshotCache() asserts the frame tree is primary.
However during WebContents destruction, the frame tree is reset before
the animator, so the navigation controller (owned by the FrameTree) back
pointer is a UAF.

This CL adds a shortcut to destroy the animator as the "first" thing
during the WebContents's destruction. Then the animator can still
perform the clean up tasks while the navigation controller is still
valid.

(cherry picked from commit 3aef1d16)

Bug: 373898450, 375188602
Change-Id: I0d793d536ca99700cf7f8c324f562131f2a480c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5948024


Commit-Queue: William Liu <liuwilliam@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1372744}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5953188
Cr-Commit-Position: refs/branch-heads/6778@{#769}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Mac Arm PGO profile from chrome-mac-arm-6778-1729770119-520d7209a099388ffb51821bd51728921961afd3-17356080.profdata to chrome-mac-arm-6778-1729777904-2cd01c1a9119763c5b857b43b09eb3aaa3400060-888c86be.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ie3279043b46f9df006011017450541723b344ab1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962557
Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#768}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

All instances of the crash are due to the overscroll actions controller
triggering an NTP scroll event in response to it being stopped. Once the
NTP is stopped, it is no longer ready to handle scroll events, thus
causing the crash.

This CL checks if the view controllers array is still populated, which
is an indicator of the NTP being stopped, and returns early on scroll
events if needed.

(cherry picked from commit cfa88be8)

Fixed: 40848296
Change-Id: Ib6e4cec142e7f99bdaeda9e8105fb200abf3732b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5954783


Reviewed-by: Chris Lu <thegreenfrog@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Auto-Submit: Adam Arcaro <adamta@google.com>
Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Cr-Original-Commit-Position: refs/heads/main@{#1372456}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962396
Commit-Queue: Adam Arcaro <adamta@google.com>
Cr-Commit-Position: refs/branch-heads/6778@{#767}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

This CL adds Most Visited Tiles scoring algorithm "Decay, Cap 1"
(maxtk@) to #most-visited-tiles-new-scoring:
* Recency factor is a decaying exponential.
* Visit count is capped to 1, i.e., we only care about whether a site
  is visited each day, and not how many times.

Feature param changes:
* Under "recency_factor": Add new value "decay".
* Add "decay_per_day" param: Double to specify how each passing day
  attenuates a visit's score contribution. Currently useful only for the
  recency_factor "decay".

Values chosen for "Decay, Cap 1":
* "decay_per_day": 0.9131007162822623 = exp(-1 / 11).
* "daily_visit_count_cap": 1.

Note: "Decay Staircase, Cap 10" essentially uses "decay_per_day" value
of 0.9355069850316178 = exp(-1 / 15). However, since experiments are
already underway and there are other parameters, so for simplicity we
left RecencyFactorDecayStaircase alone (instead of adapting it to use
"decay_per_day").

Code changes, including some refactoring:
* SegmentScorer:
  * Change CTOR to take RecencyFactor instead of name; update callers.
  * static CreateFromFeatureFlags(): Extract RecencyFactor-related logic
    to new function RecencyFactor::CreateFromFeatureFlags().
  * Add RecencyFactorDecay.
  * RecencyFactor: Add static CreateFromFeatureFlags()

Testing: SegmentScorerTest:
* Change to use ScopedFeatureList. Now tests instantiate SegmentScorer
  with CreateFromFeatureFlags() instead of calling the CTOR.
* Add 1 new test.

(cherry picked from commit 3209cbe9)

Bug: 373852494
Fixed: 375238481
Change-Id: Ie59e53a1c6d8886fac2a34a4a55ae2be86264676
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5939073


Commit-Queue: Samuel Huang <huangs@chromium.org>
Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1369590}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5957890
Cr-Commit-Position: refs/branch-heads/6778@{#766}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Mac PGO profile from chrome-mac-6778-1729706343-79c24d39ddefe100f5776dbac5d5dd2c0b8d69d6-c4f66504.profdata to chrome-mac-6778-1729770119-d924c8b8624d6c7e99235ff89a6932206445b2e3-17356080.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m131.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I55e767b35f9f4d6a665b45f9e43e5c06635cbbc5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5961923
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#765}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729774102-c778cc1e35f232ab57c67aa5fc880a2d8620f423-edca7b9f.profdata to chrome-android64-6778-1729776239-0e2175d43508a0701fee1dfe6df8d6df29710b80-a2dfde63.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: I74b3bab65a54b9a1736b1bbb4fabf60bcb3570b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5960234
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#764}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Usually, justify-self causes an element to shrink-to-fit in the absence
of a preferred size. But we have to let an inline child of the justified
element stretch so that any of _its_ block children can still stretch to
the justified grandparent.

(cherry picked from commit 921f8733)

Fixed: 374034249
Change-Id: I17b7fa89d84a76eacff2d2e6448db1b7bfe46a32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5942095


Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1370819}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962296


Auto-Submit: David Grogan <dgrogan@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/branch-heads/6778@{#763}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll ChromeOS Bigcore AFDO profile from 131-6778.0-1729474663-benchmark-131.0.6778.15-r1 to 131-6778.0-1729474663-benchmark-131.0.6778.16-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-bigcore-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I3948c0c064415fa6470f74f6ea9db6293e4f52c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962103
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#762}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Linux PGO profile from chrome-linux-6778-1729749474-9757f30b9fbd17c2061b6218d133c0ad6441fdbd-a526e8e9.profdata to chrome-linux-6778-1729770119-b8ff6b2a0122607d90160145115a928733baf7f7-17356080.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m131.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I00577e9737fd578918d689448608586b56eb5e26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962201
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#761}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729771354-e1a7c05b255570c138bfac064e6a675e3c255de0-f9fffe8e.profdata to chrome-android64-6778-1729774102-c778cc1e35f232ab57c67aa5fc880a2d8620f423-edca7b9f.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ia2e676f363346cbb1ce9c59dba176cea68cc8089
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5960229
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#760}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll Chrome Android ARM64 PGO profile from chrome-android64-6778-1729768610-6c37619c71529d0f310ceb9934fc62d0b0292850-c1ee480b.profdata to chrome-android64-6778-1729771354-e1a7c05b255570c138bfac064e6a675e3c255de0-f9fffe8e.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: pgo-profile-sheriffs@google.com
Change-Id: I737e6301b0c328d96e1e20add089703d429bd82d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962199
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#759}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}

Roll ChromeOS Atom AFDO profile from 131-6778.0-1729477565-benchmark-131.0.6778.15-r1 to 131-6778.0-1729477565-benchmark-131.0.6778.16-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I1644f6c0688e50dd9ace450a7238e4ebfd5d74a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5962098
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6778@{#758}
Cr-Branched-From: b21671ca-refs/heads/main@{#1368529}