1.22% Base Content Heap Unclassified (Linux) regression on Wed October 23 2024
Categories
(Core :: XPCOM, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox132 | --- | unaffected |
firefox133 | --- | affected |
firefox134 | --- | affected |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(Keywords: perf, perf-alert, regression)
Perfherder has detected a awsy performance regression from push 34bd268d67080cbdffa1edc4bf96dcd1964ad1e4. 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) |
---|---|---|---|---|
1% | Base Content Heap Unclassified | linux1804-64-shippable-qr | fission | 2,330,388.00 -> 2,358,913.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.
You can run all of these tests on try with ./mach try perf --alert 42371
The following documentation link provides more information about this command.
For more information on performance sheriffing please see our FAQ.
If you have any questions, please do not hesitate to reach out to bacasandrei@mozilla.com.
Updated•12 days ago
|
Comment 1•12 days ago
|
||
Set release status flags based on info from the regressing bug 1924821
Comment 2•6 days ago
|
||
This is fine, since without this we need to allocate that much memory (more actually) at runtime
Updated•6 days ago
|
Comment 3•6 days ago
|
||
(In reply to Randell Jesup [:jesup] (needinfo me) from comment #2)
This is fine, since without this we need to allocate that much memory (more actually) at runtime
This is about heap-unclassified, not resident memory, so the underlying issue here is that we don't have a memory report for MOZ_LOG. That's a preexisting issue and not a huge deal, so a WONTFIX here is fine. I'll file a bug for it and link it here.
Description
•