2.52% damp custom.jsdebugger.with-wrap-editor.scroll.DAMP (Linux) regression on Tue September 1 2026
Categories
(Core :: Memory Allocator, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | unaffected |
| firefox155 | --- | unaffected |
| firefox156 | --- | unaffected |
| firefox157 | --- | affected |
People
(Reporter: performance-sheriff-bot, Unassigned)
References
(Regression)
Details
(4 keywords)
Perfherder has detected a devtools performance regression from push d04c97347dcc984bc6a4d49fa0933411f715727b. 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] |
|---|---|---|---|---|
| 3% | damp custom.jsdebugger.with-wrap-editor.scroll.DAMP (doc) | linux2404-64-shippable | e10s fission stylo webrender | 511.47 ms -> 524.34 ms |
| Improvement | Test | Platform | Options | Absolute values [old vs new] |
|---|---|---|---|---|
| 4% | damp custom.jsdebugger.pretty-print.reload-and-pause.DAMP (doc) | linux2404-64-shippable | e10s fission stylo webrender | 3,529.61 ms -> 3,390.34 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 52553(See documentation link for details). - Test locally: To run the tests locally use
./mach perftest 52553 - Profiling jobs: Trigger jobs from Treeherder job view or request them from aesanu@mozilla.com.
Comment 1•2 months ago
|
||
Set release status flags based on info from the regressing bug 2055507
Comment 2•2 months ago
|
||
I'm not sure why any test would regress with this change, unless it's getting very unlucky with the timing of the idle purge.
Given there's a bunch improvements reported on the main Bug 2055507 I don't think there's any action we need to take.
Description
•