The members in this function have sequence checker guards now, which
requires our own overrides to have the CHECK before accessing them.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/0d7e6fde0d0995dfbe26a32aa3e425b4229abbc3
commit 0d7e6fde0d0995dfbe26a32aa3e425b4229abbc3
Author: Joe Mason <joenotcharles@google.com>
Date: Thu Oct 30 11:14:14 2025 -0700
Allow DeviceInfoSyncBridge pulses to run at BEST_EFFORT priority
Field data shows that DeviceInfoSyncBridge::SendLocalData is a large
source of congestion (~0.14% of all browser process task congestion). To
reduce congestion, this patch pipes a SequencedTaskRunner through from
the chrome/ layer, to use for scheduling this function. The ReducePPMs
experiment sets it to a BEST_EFFORT task queue. Outside the experiment
this should be a no-op since it uses the default main thread task queue.
Also adds a SEQUENCE_CHECKER to DeviceInfoSyncBridge to make sure this
doesn't break any sequencing guarantees.
Bug: 441949788
Change-Id: Ib0a6c7d40eb08a8f0a0bbaf2619c30f90b7d26e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7088428
Commit-Queue: Joe Mason <joenotcharles@google.com>
Reviewed-by: Jood Hajeer <jood@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1538074}
Claudio DeSouza
d3cbd0baf7