Closed Bug 1635678 Opened 5 years ago Closed 4 years ago

3.2 - 3.68% Heap Unclassified (windows10-64-shippable) regression on push 5f1618cc19f5d34eedb2dc62dd64043b62af4e48 (Fri May 1 2020)

Categories

(Core :: DOM: CSS Object Model, defect)

defect

Tracking

()

RESOLVED FIXED
mozilla78
Tracking Status
firefox-esr68 --- unaffected
firefox75 --- unaffected
firefox76 --- unaffected
firefox77 --- unaffected
firefox78 --- fixed

People

(Reporter: marauder, Assigned: nordzilla)

References

(Regression)

Details

(Keywords: perf, perf-alert, regression)

Perfherder has detected a awsy performance regression from push 5f1618cc19f5d34eedb2dc62dd64043b62af4e48. As author of one of the patches included in that push, we need your help to address this regression.

Regressions:

4% Heap Unclassified windows10-64-shippable opt 50,035,948.69 -> 51,877,529.43
3% Heap Unclassified windows10-64-shippable opt 50,046,108.22 -> 51,767,165.13
3% Heap Unclassified windows10-64-shippable opt tp6 68,458,190.91 -> 70,646,151.29

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 offending patch(es) will be backed out in accordance with our regression policy.

For more information on performance sheriffing please see our FAQ.

Blocks: 1628613
Component: Performance → DOM: CSS Object Model
Flags: needinfo?(enordin)
Product: Testing → Core
Regressed by: 1632686
Version: Version 3 → unspecified
Has Regression Range: --- → yes
Depends on: 1636266

[Bug 1632686] introduced behavior where StyleSheets are cloned before they are put into the XUL cache [here].

It's understandable that this would cause more overall heap allocations. I am looking into whether memory reporting the XUL cache will improve these numbers in [Bug 1636266].

I find it curious that the alert was triggered only for Windows10-64.

Flags: needinfo?(enordin)

It looks like adding memory reporting to the StyleSheets in the XUL cache in [Bug 1636266] will re-classify this unclassified memory, based on these comparisons:

https://treeherder.mozilla.org/perf.html#/compare?originalProject=try&originalRevision=80c975e1b1a430686d0a9ae71285bfb65e224abb&newProject=try&newRevision=a2a12252705d9ca8e89cdf2a12a21a2896c8857c&framework=4

I expect that this regression will be fixed once that patch lands.

The patch has landed.

marauder, can you double check that you are no longer seeing this issue?

Flags: needinfo?(marian.raiciof)
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(marian.raiciof)
Resolution: --- → FIXED
Assignee: nobody → enordin
Target Milestone: --- → mozilla78
You need to log in before you can comment on or make changes to this bug.