2.29% damp browser-toolbox.webconsole-ready.DAMP (Linux) regression on Wed January 21 2026
Categories
(Core :: Machine Learning: Frontend, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox147 | --- | unaffected |
| firefox148 | --- | unaffected |
| firefox149 | --- | fix-optional |
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(4 keywords)
Perfherder has detected a devtools performance regression from push 0080df0e5323fc6a3b41e5ff97602341d41ea3ca. 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] |
|---|---|---|---|---|
| 2% | damp browser-toolbox.webconsole-ready.DAMP (doc) | linux1804-64-shippable-qr | e10s fission stylo webrender | 457.90 ms -> 468.39 ms |
Support & Actionable Steps
For questions, please contact aesanu@mozilla.com. You can also find help on Slack (#perf-help) or Matrix (#perftest).
Action guide details:
- See the guide to handling regression bugs for investigation steps.
- Review the alert summary for affected tests, graphs, and comparisons.
- Check the PerfCompare results.
- Tests on Try: Run all tests using
./mach try perf --alert 48314(See documentation link for details). - Profiling jobs: Trigger jobs from Treeherder job view or request them from aesanu@mozilla.com.
Comment 1•9 months ago
|
||
Set release status flags based on info from the regressing bug 2008929
Comment 2•9 months ago
|
||
It has been over 7 days with no activity on this performance regression.
:flozia, since you are the author of the regressor, bug 2008929, which triggered this performance alert, could you please provide a progress update?
If this regression is something that fixes a bug, changes the baseline of the regression metrics, or otherwise will not be fixed, please consider closing it as WONTFIX. See this documentation for more information on how to handle regressions.
For additional information/help, please needinfo the performance sheriff who filed this alert (they can be found in comment #0), or reach out in #perftest, or #perfsheriffs on Element.
For more information, please visit BugBot documentation.
Comment 3•9 months ago
|
||
DevTools team member here, I think this is fine, no need to revert Bug 2008929 here
This perf test checks the opening of the Browser Toolbox (e.g. DevTools for the whole Firefox UI), so adding things in Firefox means we might have more things to consume/render in the Browser Toolbox, hence the (small) perf regression here
Updated•9 months ago
|
Updated•9 months ago
|
Comment 4•9 months ago
|
||
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #3)
DevTools team member here, I think this is fine, no need to revert Bug 2008929 here
This perf test checks the opening of the Browser Toolbox (e.g. DevTools for the whole Firefox UI), so adding things in Firefox means we might have more things to consume/render in the Browser Toolbox, hence the (small) perf regression here
Agreed with Nicolas here, most likely not a real regression.
Updated•9 months ago
|
Description
•