Closed Bug 1864158 Opened 2 years ago Closed 2 years ago

4.76 - 2.46% Base Content Resident Unique Memory / Base Content Resident Unique Memory + 3 more (Linux, Windows) regression on Tue November 7 2023

Categories

(Core :: Internationalization, defect)

defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox-esr115 --- unaffected
firefox119 --- unaffected
firefox120 --- unaffected
firefox121 + fixed

People

(Reporter: bacasandrei, Unassigned)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

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

Regressions:

Ratio Test Platform Options Absolute values (old vs new)
5% Base Content Resident Unique Memory windows11-64-2009-shippable-qr fission 10,365,952.00 -> 10,859,008.00
4% Base Content Explicit linux1804-64-shippable-qr fission 9,782,288.00 -> 10,218,000.00
4% Base Content Explicit windows11-64-2009-shippable-qr fission 10,526,053.33 -> 10,979,173.33
4% Base Content Explicit linux1804-64-shippable-qr fission 9,785,360.00 -> 10,198,032.00
2% Base Content Resident Unique Memory linux1804-64-shippable-qr fission 14,966,528.00 -> 15,334,229.33

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 patch(es) may be backed out in accordance with our regression policy.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

For more information on performance sheriffing please see our FAQ.

Flags: needinfo?(andrebargull)

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

This seems like a pretty significant hit on memory usage. We probably need a better of understand of what's causing the regression here.

The bug is marked as tracked for firefox121 (nightly). We have limited time to fix this, the soft freeze is in 2 days. However, the bug still isn't assigned.

:Amir, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Flags: needinfo?(ahabibi)

(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #4)

The bug is marked as tracked for firefox121 (nightly). We have limited time to fix this, the soft freeze is in 2 days. However, the bug still isn't assigned.

Bug 1859752 was backed-out because of bug 1864612, so we no longer have to worry about the soft freeze.

Flags: needinfo?(andrebargull)
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Flags: needinfo?(ahabibi)

Upstream bug report to investigate the heap memory increase: https://unicode-org.atlassian.net/jira/software/c/projects/ICU/issues/ICU-22647

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