Closed
Bug 1003155
Opened 10 years ago
Closed 10 years ago
Firefox 31 memory usage increase since April 27th
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(firefox31+ verified, firefox32+ verified)
People
(Reporter: ioana_damy, Assigned: mihaelav)
References
Details
(Keywords: perf, regression)
Both explicit and resident memory usage increased for Firefox 31 with 9 to 15MB starting with April 27th. Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0e91262606a6&tochange=c67a79064fd4 Reports: http://mozmill-daily.blargon7.com/#/endurance/reports?app=All&branch=31.0&platform=All&from=2014-04-26&to=2014-04-27 Notes: 1. This happens on all the platforms. 2. Not reproducible on Firefox 29 and 30. 3. I am currently investigating this issue locally and will update the bug as soon as I have more details.
Comment 2•10 years ago
|
||
Ioana, have you made progress on the investigation? It would be good if we can get a closer range, preferable on inbound for that regression.
status-firefox31:
--- → affected
status-firefox32:
--- → affected
tracking-firefox31:
--- → ?
tracking-firefox32:
--- → ?
Flags: needinfo?(ioana.budnar)
Updated•10 years ago
|
Assignee | ||
Comment 4•10 years ago
|
||
The memory regression was caused by https://hg.mozilla.org/integration/mozilla-inbound/rev/483210d830f0. Endurance results: * with 483210d830f0: Explicit memory (MB): Minimum: 97 / Maximum: 240 / Average: 142 Resident memory (MB): Minimum: 221 / Maximum: 404 / Average: 292 http://mozmill-crowd.blargon7.com/#/endurance/report/ca725ca957252135fc72c3c08f3af8c0 * with the last inbound build before 483210d830f0: Explicit memory (MB): Minimum: 92 / Maximum: 197 / Average: 128 Resident memory (MB): Minimum: 221 / Maximum: 352 / Average: 280 http://mozmill-crowd.blargon7.com/#/endurance/report/ca725ca957252135fc72c3c08f535e99 This was backed out from Firefox 31 (Aurora) on the 5th of May in bug 984537 for memory regressions. Our endurance tests show the decrease in the memory consumption since the 6th of May. Marking as FIXED (by the backout: https://bugzilla.mozilla.org/show_bug.cgi?id=984537#c28)
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ioana_damy)
Resolution: --- → FIXED
Updated•10 years ago
|
Great work, Mihaela! Looks like a new fix has landed on mozilla-central and they're seeking approval for mozilla-aurora uplift. Can you confirm this hasn't re-regressed on Nightly?
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #5) > Great work, Mihaela! Looks like a new fix has landed on mozilla-central and > they're seeking approval for mozilla-aurora uplift. Can you confirm this > hasn't re-regressed on Nightly? The memory consumption did not increase onNightly, nor on Aurora
Marking verified based on comment 6. Thanks for your help, Mihaela.
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•