chromium.gpu
| Legend: | Passed | Failed | Running | Exception |
[Blink] Have HTMLCanvasElement call GetOrCreateCRP() explicitly
It currently does this indirectly by calling
CanvasRenderingContext::IsCanvas2DResourceValid() [1]. There are two
problems with this indirection:
* It looks like a simple accessor but it's actually mutating state
* More importantly, if we were ever to get here and need to wake up
from hibernation it's flat-out *wrong*, as it won't recreate the CRP
and we'll crash later on in the method.
Of course, we want to eliminate HTMLCanvasElement explicitly asking for
the CRP to be created here in the medium term, but that's a distinct
challenge that is made more visible by this change.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/6780628/1/third_party/blink/renderer/modules/canvas/canvas2d/canvas_rendering_context_2d.cc
Bug: 352263194
Change-Id: Icfb64288a9d58ae98774ab9d455e6b3d012fe002
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781227
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491275}
[Blink] Streamline CanvasRenderingContext2D::IsCanvas2DResourceValid()
The code being removed here is redundant, as
GetOrCreateCanvasResourceProvider() will already fail in both of these
cases [1] (note: IsContextBeingRestored() will be true only here [2],
which is distinct from IsCanvas2DResourceValid() callsites).
[1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/canvas/canvas2d/canvas_rendering_context_2d.cc;l=1288-1307;drc=4eaa7ecc4adc54dc936063562327f3d0c599f403
[2] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/canvas/canvas2d/base_rendering_context_2d.cc;l=272-273;drc=a3c9c4dcd0d6de500f41d7272d9515b6b81b7729
Bug: 352263194
Change-Id: I0aa185032e19206d8cdb886841139f6a5b349a8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780628
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491274}
[Blink] Eliminate BaseRC2D::IsCanvas2DBufferValid()
This method is confusing:
* The CanvasRenderingContext2D and OffscreenCanvasRenderingContext2D
implementations are very different.
* CanvasRenderingContext2D has a very similar (but not identical)
IsCanvas2DResourceValid(), and it's not clear what the differences in
semantics would rationally be.
This CL eliminates the method by:
* Removing using it as an early out in
BaseRenderingContext2D::putByteArray()
* Inlining its respective impls at the front of
(Offscreen)CanvasRenderingContext2D::WritePixels().
BaseRC2D::putByteArray() just calls through to WritePixels(), and
WritePixels() has no other callers.
Bug: 352263194
Change-Id: Id5c4b9110ca57d70785e9cbf142d193824fe9fbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781184
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491273}
[//ui] Remove CreateBufferAsync()
Nothing uses this method at this point.
Bug: 404905709
Change-Id: Ib708981c93ea45aba912498447e05ff15f7a6b18
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780901
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491272}
[Blink] Eliminate calling ImageBitmapRenderingContext::IsAccelerated()
The one callsite of this method for ImageBitmapRenderingContext is here
[1]. That method's one production callsite is here [2]. The
ImageBitmapRC implementation of IsAccelerated() checks whether the
context's CanvasResourceProvider exists and is accelerated. However,
ImageBitmapRenderingContext creates its CRP only when pushing a frame
for OffscreenCanvas (i.e., offscreen canvas with a placeholder). Hence,
the current behavior when the source is an ImageBitmap canvas is the
following:
* HTMLCanvasElement: will never accelerate
* OffscreenCanvas with placeholder: Will accelerate if source image is
accelerated, but this is essentially coincidental (e.g., we are
looking to remove usage of CRP in that flow in the near-term)
* OffscreenCanvas without placeholder: Will never accelerate
This CL changes this flow to use whether the source image is
texture-backed to determine whether the source is accelerated for
source ImageBitmap canvases. This fixes the flows described above.
[1] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/canvas/canvas_rendering_context_host.cc;l=186;drc=d0cdb873a9f5d9b6ef2696f65cdd80b619240b14;bpv=1;bpt=1
[2] https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/canvas/html_canvas_element.cc;l=1924;drc=d0cdb873a9f5d9b6ef2696f65cdd80b619240b14
Bug: 352263194
Change-Id: If422849649bb387d0963f542377b60e0e4129779
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779344
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491271}
[//ui] Remove CreateNativePixmapAsync()
Nothing uses this method at this point.
Bug: 404905709
Change-Id: I3bc05430fd42719f4f6cb53ece321ebe8ad8debe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780941
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491270}
[//media] Re-enable tests on Mac
The tests set an 8-bit value but read it back as a 16-bit value,
assuming that the "unset half" of the value is 0. Zero-initialize the
data in question rather than leaving it uninitialized in order to make
this work as expected.
Bug: 366375486
Change-Id: I511e5b6278af54fcfe8ed8930d4f0c125b530c16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6771798
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491269}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-main-1753293557-1e5f5de80b7fe2c07413d277b32fb2f829caace6-130e6845bbaaef3059f8518d8c550d9f4084401f.profdata to chrome-win32-main-1753314684-35ef504bcfd964c8692b76560fdea8511850a5b5-701ac6259b6182382cbebd32369b58c64a99d12f.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
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 main 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.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Ie0208c0f1363821ddc4c18c2b0307e2126d418fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777899
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/heads/main@{#1491268}
Disable a test in DeepScanningReportingSourceTypeTest on Windows
This CL disables
`DeepScanningReportingSourceTypeTest.ProcessesResponseCorrectly` due to
flakiness.
Bug: 433865922
Change-Id: I6568ef700ed66be9bded3c5d8121beb0d1b97f74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782065
Reviewed-by: Shunya Shishido <sisidovski@chromium.org>
Owners-Override: Keita Suzuki <suzukikeita@chromium.org>
Commit-Queue: Shunya Shishido <sisidovski@chromium.org>
Auto-Submit: Keita Suzuki <suzukikeita@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491267}
Roll V8 from 34526631fbd7 to 75f58bf8c6dd (4 revisions)
https://chromium.googlesource.com/v8/v8.git/+log/34526631fbd7..75f58bf8c6dd
2025-07-24 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Version 14.0.300
2025-07-24 yahan@iscas.ac.cn [riscv] Optimize emit of sext.w when CompareZero/WordShl/Word32Shr/Word32Sar
2025-07-23 manishearth@google.com [temporal] Use new get_epoch_ns_for() API for Intl
2025-07-23 jkummerow@chromium.org [wasm-custom-desc] Add ConfigureAllPrototypesOpt builtin
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/v8-chromium-autoroll
Please CC liviurau@google.com,machenbach@google.com,v8-waterfall-gardener@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://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.chromium.try:linux-blink-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:dawn-linux-x64-deps-rel;luci.chrome.try:linux-perf-trigger
Change-Id: I3e3aa3e5cc74941b8067c3aa6f065b265bc9a2ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782619
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/heads/main@{#1491266}
Roll Depot Tools from 5ce80c825163 to 9cf131bdaadf (1 revision)
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/5ce80c825163..9cf131bdaadf
2025-07-24 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC chops-source-team@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: 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.chromium.try:linux-utr-tester;luci.chromium.try:win-utr-tester
Bug: None
Tbr:
Change-Id: I3490d38ec66f89ba764a8306c3f7cedc1c358320
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782028
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/heads/main@{#1491265}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-main-1753282773-9ff150ff83e0015e7bf29c3a08593d4b1b6cc8ff-32093f0b1887f58ac9849a01921abe9ebdd6e770.profdata to chrome-win64-main-1753314684-04721f8770c75f2c9f247c8dd591c3efda4071bf-701ac6259b6182382cbebd32369b58c64a99d12f.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
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 main 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.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Idd1203eceb95b43d380cc52ef7b111551670096b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782153
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/heads/main@{#1491264}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753327782-11ce9f6d91fa4d90ca5289625ce9c6db0e6617b9-cff8173dc17c32f64c910b116c5ef05fb56daddd.profdata to chrome-android64-main-1753331281-bee8d7e01f86d5a4e7577f1a05d677a34f86d8ce-30b32007873b6e86ecc636deef4814b60cfd0916.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
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 main 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
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I13c5d0e5935ecbd48fdb1a3864f94fa387cbc99d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782264
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/heads/main@{#1491263}
Remove unused include in preconnect_manager_impl.cc
Should save ~5 MiB of compiler input size.
Bug: 40318405
Change-Id: Iad00848e039d3e6c494b1a24d9ffe5540507f6b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782507
Commit-Queue: David Sanders <dsanders11@ucsbalum.com>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491262}
Roll goldctl (mac) from B7EcDAL2Fh_20K0Ud... to hZpj0hRnYNFplpUOc...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/goldctl-mac-chromium-autoroll
Please CC bsheedy@chromium.org,kjlubick@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in goldctl (mac): https://bugs.chromium.org/p/skia/issues/entry?owner=kjlubick@google.com
To file a bug in Chromium: 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
Bug: None
Tbr: bsheedy@chromium.org
Change-Id: I98041e398c3f968ca9b930591b726d39937811a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782621
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/heads/main@{#1491261}
[CompositeClipPathAnimation] Add test for setStartTime
Related to recent fixes for animation retargets, this test
ensures JS calls to setStartTime do not cause unexpected issues
with cc clip path animations
Bug: 40503852
Change-Id: Id95bd0b91f83931dcd0d73a76f3551405f1dbb68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6732684
Commit-Queue: Claire Chambers <clchambers@microsoft.com>
Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491260}
Roll Infra from e7eba484af07 to efbba6418643
https://chromium.googlesource.com/infra/infra.git/+log/e7eba484af07..efbba6418643
2025-07-24 chromium-autoroll@skia-public.iam.gserviceaccount.com Roll luci-go from f801a0983385 to af7df56f923e (1 revision)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/infra-chromium
Please CC iannucci@google.com,luci-eng@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: 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: iannucci@google.com
Change-Id: I1cf99400e4c69c6103bbd1752b6806b84a01c723
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782259
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/heads/main@{#1491259}
[CompositeClipPathAnimation] Add tests for setting time & duration
This CL adds 3 tests that cause the animation to change out of its
current state, either before or after the active phase, to ensure
correctness for composited clip path animations.
Bug: 40503852
Change-Id: Iba5cb8a192e27d0c01911e54707389abeaa88c97
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6732702
Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: Claire Chambers <clchambers@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1491258}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753322388-1c8ee100d641d8df0e257144a45ced880f5ff181-0b50b83d7110b9015ccd0903bc9a4b1412d4c69b.profdata to chrome-mac-arm-main-1753329296-e7d8a6dec1d78ec51d8771e01b67e408e89cd1e4-bad989a1109bce64b0f0dc9c54fe344034832127.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
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 main 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.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I555bc332150b0278263fbc4a2f24123f0526f39d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782505
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/heads/main@{#1491257}
Turn HarfBuzz given range `DCHECK` to `CHECK` (part 2)
crrev.com/c/6782438 missed one more variant of
`HarfBuzzShaper::Shape()`. This patch changes it to `CHECK`.
Bug: 433647419
Change-Id: I8f826ad7eb94883e87ff56de76798b7c47fe2a0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780169
Commit-Queue: Kent Tamura <tkent@chromium.org>
Auto-Submit: Koji Ishii <kojii@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491256}
Roll DevTools Frontend from eb970fbc6482 to 8809501a6cd8 (1 revision)
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/eb970fbc6482..8809501a6cd8
2025-07-24 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Roll browser-protocol
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 liviurau@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://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
Bug: None
Change-Id: I51fb4d6357444223d68119d4c4edbfae3d4230d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782626
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/heads/main@{#1491255}
Make fields of `ShapeResultRun` private
All fields were public for historical reasons. This patch
changes them to private, with some deeply integrated classes
added to friends.
This patch has no behavior changes.
Change-Id: Ic4710568fd76ee629f85dffcbace5227c42d74e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6777481
Reviewed-by: Kent Tamura <tkent@chromium.org>
Auto-Submit: Koji Ishii <kojii@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491254}
Roll goldctl (mac arm64) from wf6bkz0nbOmOa5raA... to ulgsu9nJXlCe-TeAX...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/goldctl-mac-arm64-chromium-autoroll
Please CC bsheedy@chromium.org,kjlubick@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in goldctl (mac arm64): https://bugs.chromium.org/p/skia/issues/entry?owner=kjlubick@google.com
To file a bug in Chromium: 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
Bug: None
Tbr: bsheedy@chromium.org
Change-Id: I938dd6121036ccdac9edb796e50e15f0d50ba7dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782620
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/heads/main@{#1491253}
[WebNN] Implement DequantizeLinear and QuantizeLinear operations for ORT backend
Bug: 432136553
Change-Id: I79abe84a0f2a732f30243d52f651ade2ab9639d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6759793
Commit-Queue: Wei4 Wang <wei4.wang@intel.com>
Reviewed-by: Phillis Tang <phillis@chromium.org>
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Cr-Commit-Position: refs/heads/main@{#1491252}
[PasswordChange] Fix toast transition glitch
Calling SetPreferredSize() on layout updates for the action button
creates a flickering effect because of the layout being invalidated and
button being drawn on the left and then moved to the right side of the
toast.
SetPreferredSize() seems unnecessary anymore given the changes to
TabDialogManager that happened in the meantime (for resizing/animating
the toast automatically on transitions), which should handle the new
preferred size after label change correctly.
Bug: b:433496206
Change-Id: I2c5bf51c22acc740313f65b57ebdeb7a711ca0d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781226
Commit-Queue: Rafał Godlewski <rgod@google.com>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491251}
Roll goldctl (linux) from Vo1Pp2yAU3s1kNKpv... to Sg25-ZztJqPtMF0rP...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/goldctl-linux-chromium-autoroll
Please CC bsheedy@chromium.org,kjlubick@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in goldctl (linux): https://bugs.chromium.org/p/skia/issues/entry?owner=kjlubick@google.com
To file a bug in Chromium: 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
Bug: None
Tbr: bsheedy@chromium.org
Change-Id: I43132955f0a9958a841374e56833236839fa0d4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782483
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/heads/main@{#1491250}
Roll goldctl (win) from eJjdTeKFcLju_kN2-... to 0sP0Mad75mVvpE0TL...
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/goldctl-win-chromium-autoroll
Please CC bsheedy@chromium.org,kjlubick@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in goldctl (win): https://bugs.chromium.org/p/skia/issues/entry?owner=kjlubick@google.com
To file a bug in Chromium: 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
Bug: None
Tbr: bsheedy@chromium.org
Change-Id: Id8440931d74dc765600e1060a3fe109b2df44b55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782482
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/heads/main@{#1491249}
Disable flaky NoCrashOnEventsDuringHandlerPrint test on Mac.
Disable the flaky test on Mac.
Bug: 433855037
Change-Id: Ia7876dedb78e7b1cefd031df5f00908531617534
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782419
Owners-Override: Keita Suzuki <suzukikeita@chromium.org>
Commit-Queue: Keita Suzuki <suzukikeita@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491248}
[PA] Move Metadata outside of GigaCage (4/6)
Replace the code for shadow metadata initialization with external
metadata one, i.e. allocates virtual address space for metadata and
initializes offsets. Remove `EnableShadowMetadata()`-related code.
Design Doc:
https://docs.google.com/document/d/1Mn-qRAWuDhS_gRL_OG2TYL-EW5D8yljaCyM40S0ocVc/edit?tab=t.0
Bug: crbug.com/40238514
Change-Id: Icca2cbbc1d7245d56202b2c451cc3e40e8624484
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6759630
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Takashi Sakamoto <tasak@google.com>
Cr-Commit-Position: refs/heads/main@{#1491247}
[PasswordChange] Update settings strings
Updates the strings to match the mocks and adds UXW description notes.
Mock: https://screenshot.googleplex.com/Aj2pTEiCrNp6d4L
Impl: https://screenshot.googleplex.com/5mGdH2XaUSfxDR7
Fixed: b:433631828
Change-Id: I6e1de4274ce626fa4777fd5a47eef01083354b8d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6779761
Commit-Queue: Rafał Godlewski <rgod@google.com>
Reviewed-by: Viktor Semeniuk <vsemeniuk@google.com>
Reviewed-by: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491246}
[Nav Bar Color Animations] Enable flag by default
Removed field trial testing config and enabled flag by default for the launch. The unit tests will fixed during the flag cleanup.
Bug: 425761643
Change-Id: I9085575203dfd93c1aa758fd0314893e98f63233
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782578
Commit-Queue: Eleanor Lee <eleanorlee@google.com>
Reviewed-by: Wenyu Fu <wenyufu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491245}
[fetch-retry] Add dedicated UseCounter for RetryOptions
According to [previous discussion][1], the `Measure` IDL annotation doesn't work for dictionary fields.
[1]: https://chromium-review.googlesource.com/c/chromium/src/+/6758857/4..13/third_party/blink/renderer/core/fetch/request_init.idl#b36
Bug: 417930271
Change-Id: Icaf750ebe50edfa4b3b56eb8ff25823b0303e96c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782308
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Ming-Ying Chung <mych@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491244}
Turn HarfBuzz given range `DCHECK` to `CHECK`
When the given range is invalid, such as `end < `start`,
HarfBuzz can cause severe errors including `SECURITY_DCHECK`.
This patch changes `DCHECK` on the entry to `CHECK`. This
makes it easier to distinguish whether errors come from
invalid arguments in the callers or from HarfBuzz itself.
Bug: 433647419
Change-Id: I0afba2ce1e0fc16f6b103d0abe4305f048066618
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782438
Auto-Submit: Koji Ishii <kojii@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491243}
audit_non_blink_usage: Reject WTF:: in new code
* WTF::* was allowed because it was not recognized as an identifier.
This CL updates a regular expression to cover WTF::*, and it is
disallowed by default.
* Update a rule for BindOnce/Repeating.
Bug: 422768753
Change-Id: Idff00ab7791d91b9105e97042e2f0a7b7f0e0a42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780182
Auto-Submit: Kent Tamura <tkent@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491242}
Replace WTF:: with blink:: in documents
This CL has no behavior changes.
Bug: 422768753
Change-Id: Ie1058bd708fa3cd6bd07d0a9173c6bab5fbbab52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780142
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491241}
Forward the return key to the omniboxKeyboardDelegate
This CL fixes a bug where the copied-link suggestion was not navigated
to when hitting the return key.
Prior to this CL, the return key was not triggering any call to
OmniboxTextFieldIOS nor its delegate. This CL adds the same explicit
handling as for arrow keys.
Fixed: 40836724
Change-Id: I1f444e9e7ec6c14468064102c02a9047b15f4c99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6773725
Reviewed-by: Christian Xu <christianxu@chromium.org>
Auto-Submit: Louis Romero <lpromero@google.com>
Commit-Queue: Louis Romero <lpromero@google.com>
Cr-Commit-Position: refs/heads/main@{#1491240}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753324191-946ce75bfc0f44d02de1ebab81b2a8335985076f-ed097db5805c04ff8d5593196598d8db0293a825.profdata to chrome-android64-main-1753327782-11ce9f6d91fa4d90ca5289625ce9c6db0e6617b9-cff8173dc17c32f64c910b116c5ef05fb56daddd.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
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 main 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
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I2f968a4a721906150ca5aee7a9873b65ffebb7a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782502
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/heads/main@{#1491239}
Roll clank/internal/apps from 08f659e4dc8f to 004095b7e48c (1 revision)
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/08f659e4dc8f..004095b7e48c
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/clank-apps-chromium-autoroll
Please CC chrome-brapp-engprod@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://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
Bug: None
Tbr:
No-Try: true
Change-Id: I51b4e78e05cb844e3dd649816e0753267ca5631e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782504
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491238}
Fix `PDFiumOnDemandSearchifier` current page unloading.
Searchifier crashes in the following scenario:
1. A previously unloaded page is sent to OCR.
2. OCR returns results.
3. The page is scheduled for print and hence the results are not
committed.
4. OCR disconnects.
5. Searchifier tries to unload the page.
To avoid the issue, verify that `current_page_` is not already reset
before trying to unload it.
Bug: 433175512
Change-Id: I354258e4d9acf560f6925a90bd22752b52d85d44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6771407
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491237}
Roll Chrome Mac Arm PGO Profile
Roll Chrome Mac Arm PGO profile from chrome-mac-arm-main-1753314684-7b1d8af4b17e9003032919fefcee7cc879b83668-701ac6259b6182382cbebd32369b58c64a99d12f.profdata to chrome-mac-arm-main-1753322388-1c8ee100d641d8df0e257144a45ced880f5ff181-0b50b83d7110b9015ccd0903bc9a4b1412d4c69b.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
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 main 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.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I2004b5b2ec69e390cd5fa4fbef7ff5aaf87a9620
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782289
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/heads/main@{#1491236}
Roll Arm AFDO from 140.0.7313.0_pre1490386_rc-r1-merged to 140.0.7314.0_pre1490791_rc-r1-merged
This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file go/crostc-bug.
Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/afdo-arm-chromium
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 Main: 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
Merge-Approval-Bypass: Chrome autoroller
Change-Id: I2b9105ae052851df55f67da486e8d945958e7f0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782568
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/heads/main@{#1491235}
Re-enable held.tentative.https.html WPT
The test is automatically added to expectations by import cl
(https://chromium-review.googlesource.com/c/chromium/src/+/6723156),
but this is not needed. It seems the update on test expected file is
added at the same day, which made the auto bot confused.
(https://chromium-review.googlesource.com/c/chromium/src/+/6713496)
Removing held.tentative.https.html from TestExpectations.
Bug: 431034520
Cq-Include-Trybots: luci.chromium.try:linux-blink-rel
Change-Id: Idfc38634c661cc2f3e1ca6a9f48632c69663eaba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780760
Auto-Submit: Eriko Kurimoto <elkurin@chromium.org>
Commit-Queue: Eriko Kurimoto <elkurin@chromium.org>
Reviewed-by: Mingyu Lei <leimy@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491234}
[DevTools] Register new badge for DevTools Ai File Assistance
Doc: go/devtools-new-badges
Bug: 427371633
Change-Id: Ib60980d4197950e132f239dbb27468ac7588f826
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780580
Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Kim-Anh Tran <kimanh@chromium.org>
Reviewed-by: Wolfgang Beyer <wolfi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491233}
Automated Commit: LKGM 16359.0.0-1070472 for chromeos.
CrOS Changes (16359.0.0-1070466 -> 16359.0.0-1070472):
- External: http://go/cros-changes/78184..78190?ext=true
- Internal: http://go/cros-changes/111872..111878
Uploaded by https://ci.chromium.org/b/8708539091012783393
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-brya-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-jacuzzi-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-reven-chrome
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-volteer-chrome
CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-octopus-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-jacuzzi-rel
CrOS-LKGM: 16359.0.0-1070472
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8708539091012783393
CrOS-External-Manifest-Position: 78190
CrOS-Internal-Manifest-Position: 111878
Change-Id: I1d344f4b9f0c46c83ef8f68f67b8e4ed99572deb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782279
Commit-Queue: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com>
Bot-Commit: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1491232}
Roll Chrome Android ARM64 PGO Profile
Roll Chrome Android ARM64 PGO profile from chrome-android64-main-1753321021-f3a0a1a87c86255b70c55837442535504c6fb4b7-53f756a550388a4308378ce3b24df0593abf62d3.profdata to chrome-android64-main-1753324191-946ce75bfc0f44d02de1ebab81b2a8335985076f-ed097db5805c04ff8d5593196598d8db0293a825.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
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 main 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
Merge-Approval-Bypass: Chrome autoroller
Change-Id: Icb009f1a65dda00e79012d642dc1ee0b1a78e4ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782558
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/heads/main@{#1491231}
Clean up unnecessary image_decoder dependency
This CL removes the chrome/browser/image_decoder dependency from:
- chrome/browser/ui/ash/shelf
- chrome/browser/ash/crosapi
Bug: b:428654878
Change-Id: I7bec450272cae4609c675b96476eff952efcb155
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780425
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Jun Ishiguro <junis@google.com>
Cr-Commit-Position: refs/heads/main@{#1491230}
Roll gn from 85f62c164c82 to 05e031634869
https://gn.googlesource.com/gn.git/+log/85f62c164c82..05e031634869
2025-07-24 thestig@chromium.org Shorten targets from //path/to/foo:foo to //path/to/foo
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/gn-chromium-autoroll
Please CC dpranke@chromium.org,dpranke@google.com,thakis@chromium.org,tikuta@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: 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: dpranke@chromium.org,thakis@chromium.org,tikuta@google.com
Change-Id: Ie75e11f8e712066cd8d30e249ce2ba31d58b5dce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6780697
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/heads/main@{#1491229}
Roll compiler-rt from f11321e08af0 to e2bc292b5860 (2 revisions)
https://chromium.googlesource.com/external/github.com/llvm/llvm-project/compiler-rt.git/+log/f11321e08af0..e2bc292b5860
2025-07-23 bblueconway@gmail.com [ASan][Darwin][GCD] Add interceptor for dispatch_apply (#149238)
2025-07-23 Jake.egan@ibm.com [sanitizer_common][nfc] Rename `tid_t` to avoid conflicting declarations (#149011)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/compiler-rt-chromium
Please CC aeubanks@google.com,lexan@google.com on the revert to ensure that a human
is aware of the problem.
To file a bug in Chromium: 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: aeubanks@google.com
Change-Id: I50783568ec8cea0a270af0177c7528fbeabe8e9b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782381
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/heads/main@{#1491228}
Remove requirement for context sharing enabled in pinned tabs cause it is broken
Bug: 433154265
Change-Id: I525b779c1ddf56f22ae7541d588d1f7095f1357d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6782100
Reviewed-by: Michael Crouse <mcrouse@chromium.org>
Commit-Queue: Sophie Chang <sophiechang@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491227}
Move wtf/wtf_size_t.h to "blink" namespace
This CL has no behavior changes.
Bug: 422768753
Change-Id: Ied36b5e69eba9af71f721a968b6a9e528f764da3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778748
Auto-Submit: Kent Tamura <tkent@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1491226}