Closed
Bug 1498982
Opened 6 years ago
Closed 6 years ago
9.11 - 9.21% Resident Memory (linux64, linux64-stylo-sequential) regression on push ba0c3051a9ed (Fri Oct 12 2018)
Categories
(Core :: Graphics, defect)
Tracking
()
VERIFIED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox62 | --- | unaffected |
firefox63 | --- | unaffected |
firefox64 | --- | fixed |
People
(Reporter: igoldan, Assigned: sotaro)
References
Details
(Keywords: perf, regression)
Attachments
(1 file, 2 obsolete files)
1.50 KB,
patch
|
nical
:
review+
|
Details | Diff | Splinter Review |
We have detected an awsy regression from push: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=81c3640eaebc47516247f546b2203ec550fdd37a&tochange=ba0c3051a9ed3b8e3120eb25d770ea459d3f719d As author of one of the patches included in that push, we need your help to address this regression. Regressions: 9% Resident Memory linux64 opt stylo 550,110,125.90 -> 600,775,321.51 9% Resident Memory linux64-stylo-sequential opt stylo-sequential 538,109,206.50 -> 587,153,892.85 You can find links to graphs and comparison views for each of the above tests at: https://treeherder.mozilla.org/perf.html#/alerts?id=16760 On the page above you can see an alert for each affected platform as well as a link to a graph showing the history of scores for this test. There is also a link to a treeherder page showing the jobs in a pushlog format. To learn more about the regressing test(s), please see: https://wiki.mozilla.org/AWSY/Tests
Reporter | ||
Updated•6 years ago
|
Component: General → Graphics
Product: Testing → Core
Reporter | ||
Updated•6 years ago
|
Flags: needinfo?(sotaro.ikeda.g)
Assignee | ||
Comment 1•6 years ago
|
||
Difference of visual seemed to cause the memory regression.
Comment 2•6 years ago
|
||
The visuals can have various buffers like front/back buffers, depth, stencil. The selected buffer depends on the actual gfx driver. With this patch we'll always use GL/WebRender compatible visuals which can raise the memory consumption.
Comment 3•6 years ago
|
||
I don't think there's a fix for that unless we disable the HW acceleration.
Reporter | ||
Comment 4•6 years ago
|
||
(In reply to Martin Stránský [:stransky] from comment #3) > I don't think there's a fix for that unless we disable the HW acceleration. So... Can we call this a wontfix then?
Comment 5•6 years ago
|
||
Is there a reason why libGL is loaded even when GL rendering is disabled?
Assignee | ||
Comment 6•6 years ago
|
||
(In reply to Karl Tomlinson (:karlt) from comment #5) > Is there a reason why libGL is loaded even when GL rendering is disabled? Yea, we could disable to load libGL when GL rendering is disabled.
Flags: needinfo?(sotaro.ikeda.g)
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → sotaro.ikeda.g
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Assignee | ||
Comment 9•6 years ago
|
||
Attachment #9017394 -
Attachment is obsolete: true
Assignee | ||
Comment 10•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&selectedJob=205707970&revision=d1dbb3c8e92c36ba8681315a7314db952f59d9f4
Assignee | ||
Updated•6 years ago
|
Attachment #9017395 -
Flags: review?(nical.bugzilla)
Updated•6 years ago
|
Attachment #9017395 -
Flags: review?(nical.bugzilla) → review+
Comment 11•6 years ago
|
||
Pushed by sikeda@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/085738995db1 Use GL/WebRender compatible visual only when it is necessary necessary r=nical
Comment 12•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/085738995db1
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Updated•6 years ago
|
status-firefox62:
--- → unaffected
status-firefox63:
--- → unaffected
status-firefox-esr60:
--- → unaffected
Reporter | ||
Comment 13•6 years ago
|
||
I confirm the push from comment 11 fixed the regressions. Thank you! == Change summary for alert #16867 (as of Tue, 16 Oct 2018 10:25:32 GMT) == Improvements: 6% Resident Memory linux64-stylo-sequential opt stylo-sequential 579,434,924.94 -> 546,685,771.36 5% Resident Memory linux64 opt stylo 590,540,933.45 -> 563,223,022.88 For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=16867
Reporter | ||
Updated•5 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•