Closed
Bug 1711135
Opened 4 years ago
Closed 4 years ago
Make GC slice reasons better reflect why they were triggered
Categories
(Core :: JavaScript: GC, defect, P3)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
91 Branch
Tracking | Status | |
---|---|---|
firefox91 | --- | fixed |
People
(Reporter: sfink, Assigned: sfink)
References
Details
Attachments
(1 file)
When a non-initial GC slice is triggered by a timer, I want it to have reason INTER_SLICE_GC. If it's triggered for some other reason, I want it to have that reason. And I don't want the reason handling to depend on whether the GC was started by Gecko in nsJSEnvironment.cpp, or internally triggered because of some allocation threshold.
Assignee | ||
Comment 1•4 years ago
|
||
Pushed by sfink@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f3dc36032901
Make GC slice reasons better reflect why they were triggered. r=smaug,jonco
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox91:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•