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

Regressions:

Improvements:

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests. Please follow our guide to handling regression bugs and let us know your plans within 3 business days, or the offending patch(es) will be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

As these are all beta flag changes not sure how we can find the exact culprit

None of them caused a similar change on autoland?

You can rule out Bug #1703944, Bug #1697074, and Bug #1707099, because those are all for enabling EV for root certificates that are being added in Firefox 90.

There's a very little chance that bug 1713820 caused this. It could only happen if temporary storage was broken so it failed to initialize and we reported a few extra lines in the browser console (only the failure reporting to the browser console is new).

Hey Alex can you check if this bug is still valid / where :Bebe made it to?

Updating regressed by based on comment 3 and comment 4.

We don't have datapoints anymore from where the alert was triggered, and considering the 2% regression, I'll close this as WONTFIX.