Closed Bug 1521524 Opened 5 years ago Closed 5 years ago

Improve our GC reason codes

Categories

(Core :: JavaScript: GC, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla66
Tracking Status
firefox66 --- fixed

People

(Reporter: jonco, Assigned: jonco)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

We should remove unused GCReasons and add new ones where appropriate so we can improve our understanding of why GCs are being triggered. I'm seeing quite a lot of 'API' reasons in testing, which isn't all that useful.

Priority: -- → P3

Remove some unused reason codes.

Attachment #9037991 - Flags: review?(sphink)

This tries to cut down on the number of 'API' reasons, except for those in test code and the shell.

Attachment #9037993 - Flags: review?(sphink)
Comment on attachment 9037993 [details] [diff] [review]
bug1521524-add-new-reasons

Review of attachment 9037993 [details] [diff] [review]:
-----------------------------------------------------------------

Yes! (Though I wonder if the default of API should even be offered.)
Attachment #9037993 - Flags: review?(sphink) → review+
Attachment #9037991 - Flags: review?(sphink) → review+
Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/868210b65236
Remove some unused GC reasons r=sfink
https://hg.mozilla.org/integration/mozilla-inbound/rev/296ce3f773e9
Replace some uses of the 'API' GC reason with more informative ones r=sfink
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: