Closed
Bug 1575794
Opened 5 years ago
Closed 5 years ago
Increase in non-incremental GCs since 13th August
Categories
(Core :: JavaScript: GC, defect, P1)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
mozilla70
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox68 | --- | unaffected |
firefox69 | --- | unaffected |
firefox70 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Telemetry shows there has been an increase in the number of non-incremental GCs since 13th August:
Assignee | ||
Comment 1•5 years ago
|
||
I missed changing this when I changed the threshold to be the incremental trigger rather than the non-incremental one. I'm not entirely sure we need this chech at all - I think it will only happen in the case where we've requested a non-incremental GC but the interrupt hasn't caused one to run yet.
Updated•5 years ago
|
Keywords: regression
Pushed by jcoppeard@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ee81fd49f90f Fix INCREMENTAL_TOO_SLOW trigger to check the non-incremental threshold r=sfink
Comment 3•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
Updated•5 years ago
|
status-firefox68:
--- → unaffected
status-firefox69:
--- → unaffected
status-firefox-esr60:
--- → unaffected
status-firefox-esr68:
--- → unaffected
Comment 4•5 years ago
|
||
== Change summary for alert #22957 (as of Wed, 04 Sep 2019 08:07:22 GMT) ==
Improvements:
2% raptor-ares6-firefox windows10-64-shippable-qr opt 59.90 -> 58.45
For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=22957
Updated•2 years ago
|
Has Regression Range: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•