Open Bug 2090050 Opened 15 days ago Updated 2 days ago

4.96 - 4.18% vpl-av1 secondFrame + 1 more (Linux) regression on Mon November 2 2026

Categories

(Core :: Privacy: Anti-Tracking, defect, P2)

defect

Tracking

()

ASSIGNED
Tracking Status
firefox-esr153 --- unaffected
firefox160 --- unaffected
firefox161 --- disabled
firefox162 --- disabled
firefox163 --- affected

People

(Reporter: performance-sheriff-bot, Assigned: timhuang)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Attachments

(2 external files)

Perfherder has detected a browsertime performance regression from push c9a8bf04e6c2227214949a4740067f6dad71433f. As author of one of the patches included in that push, we need your help to address this regression.

Please acknowledge, and begin investigating this alert within 3 business days, or the patch(es) may be backed out in accordance with our regression policy.

Regression Test Platform Options Absolute values [old vs new] Performance Profiles
5% vpl-av1 secondFrame (doc) linux2404-64-shippable cold fission webrender 259.10 -> 271.96 Before/After
4% vpl-av1 secondFrame (doc) linux2404-64-shippable cold fission webrender 260.31 ms -> 271.17 ms Before/After

Support & Actionable Steps

For questions, please contact fbilt@mozilla.com. You can also find help on Slack (#perf-help) or Matrix (#perftest).

Action guide details:

Flags: needinfo?(tihuang)

Set release status flags based on info from the regressing bug 2053164

Severity: -- → S3
Priority: -- → P2
Assignee: nobody → tihuang
Status: NEW → ASSIGNED
Flags: needinfo?(tihuang)

This patch makes importAllLists() and getListBytes() share a single
in-flight RemoteSettings get(). UpdateFeatures() calls getListBytes() once
per list of every active feature, and each call ran its own get(). On a cold
start that put about 28 IndexedDB transactions on the parent main thread
during the first navigation, delaying the new content process and
regressing vpl-av1 secondFrame. The promise is dropped once it settles, so
later calls still read current data.

This patch makes SafeBrowsing and ContentBlockingPrefs skip changes to the
privacy.trackingprotection.content.* prefs. Both observe the whole
privacy.trackingprotection branch but read none of these prefs, so each of
the six writes from ContentClassifierPrefMirror::Sync() reran
SafeBrowsing.readPrefs() and ContentBlockingPrefs.matchCBCategory() on the
parent main thread during the first navigation of a cold start, delaying the
page's first paint.

Set release status flags based on info from the regressing bug 2053164

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: