1883308 - 28.5 - 8.25% damp console.typing / damp console.autocomplete + 2 more (Linux) regression on Wed February 28 2024

Status: NEW

(Core :: Widget: Gtk, defect)

Description

[Nicolas Chevobbe [:nchevobbe]]

Perfherder has detected a devtools performance regression from push 2356949f5c6d9a4f229d012051bac51b3eb83aec. 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)
29%	damp console.typing	linux1804-64-shippable-qr	e10s fission stylo webrender	423.05 -> 543.63
27%	damp console.typing	linux1804-64-shippable-qr	e10s fission stylo webrender-sw	408.36 -> 518.74
8%	damp console.autocomplete	linux1804-64-shippable-qr	e10s fission stylo webrender-sw	715.51 -> 775.82
8%	damp console.autocomplete	linux1804-64-shippable-qr	e10s fission stylo webrender	721.51 -> 781.07

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 these tests on try with ./mach try perf --alert 41620

For more information on performance sheriffing please see our FAQ.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 2

[Martin Stránský [:stransky] (ni? me)]

This is expected, see Bug 1882462. We delete layer manager instead of keeping it and pile up hundreds of MB per popup. It can be changed when Bug 1654938 is fixed (provide shared web render content for windows).

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Note that you can easily get 1-2GB memory permanently used by Firefox just by opening menus/popups etc. It's usually 200MB per popup.