Open Bug 2091324 Opened 10 days ago Updated 5 hours ago

11.02 - 2.16% damp custom.jsdebugger.stepOut.DAMP + 6 more (OSX) regression on Wed November 4 2026

Categories

(DevTools :: General, defect, P3)

defect

Tracking

(firefox-esr115 unaffected, firefox-esr153 unaffected, firefox160 unaffected, firefox161 wontfix, firefox162 wontfix)

Tracking Status
firefox-esr115 --- unaffected
firefox-esr153 --- unaffected
firefox160 --- unaffected
firefox161 --- wontfix
firefox162 --- wontfix

People

(Reporter: performance-sheriff-bot, Unassigned)

References

(Regression)

Details

(4 keywords)

Perfherder has detected a devtools performance regression from push 83b42279434fd7d148e33178126c97d6ef57e4e1. 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]
11% damp custom.jsdebugger.stepOut.DAMP (doc) macosx1500-aarch64-shippable e10s fission stylo webrender 156.54 ms -> 173.80 ms
9% damp custom.jsdebugger.stepOut.big-bundle.DAMP (doc) macosx1500-aarch64-shippable e10s fission stylo webrender 186.33 ms -> 203.75 ms
8% damp custom.jsdebugger.stepIn.big-bundle.DAMP (doc) macosx1500-aarch64-shippable e10s fission stylo webrender 615.80 ms -> 662.43 ms
6% damp custom.jsdebugger.pretty-print.reload-and-pause.DAMP (doc) macosx1500-aarch64-shippable e10s fission stylo webrender 1,198.93 ms -> 1,269.01 ms
5% damp custom.jsdebugger.stepOver.big-bundle.DAMP (doc) macosx1500-aarch64-shippable e10s fission stylo webrender 178.67 ms -> 186.72 ms
4% damp custom.jsdebugger.stepInNewSource.DAMP (doc) macosx1500-aarch64-shippable e10s fission stylo webrender 423.22 ms -> 441.88 ms
2% damp custom.jsdebugger.pause.DAMP (doc) macosx1500-aarch64-shippable e10s fission stylo webrender 171.73 ms -> 175.44 ms

Support & Actionable Steps

For questions, please contact fbilt@mozilla.com. You can also find help on Slack (#perf-help) or Matrix (#perftest).

Action guide details:

Flags: needinfo?(vpollet)

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

Looking at the graphs, we get some changes that might come from Bug 2028789 (which could explain the bimodality), but on other graphs, it seems pretty clear that this pushlog is responsible for some changes in the tests numbers
Alex is going to do some profiling to see what's happening

Component: Machine Learning: On Device → General
Product: Core → DevTools
Regressed by: 2028789

Feel free to needinfo me again for anything

Flags: needinfo?(vpollet)

Hi Nicolas, could you just help with setting severity/priority on this one? Much appreciated.

Flags: needinfo?(nchevobbe)

this looks more like a problem in the tes harness than a real performance regression

Severity: -- → S3
Flags: needinfo?(nchevobbe)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.