Open Bug 1892315 Opened 10 months ago Updated 2 months ago

Consider migrating GC params to static prefs

Categories

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

task

Tracking

()

People

(Reporter: jonco, Unassigned)

References

(Blocks 1 open bug)

Details

Currently we have a system of GC parameters: https://searchfox.org/mozilla-central/source/js/public/GCAPI.h#70-477

We could consider moving these to the new system of SM static prefs added in bug 1877193.

It's not clear how the current system of defaults and conversions from param value to the value stored in GCTunables would work though. If this is a problem them we could migrate those parameters that are not affected.

Also this would require some way of setting them from the JS shell.

(In reply to Jon Coppeard (:jonco) from comment #0)

It's not clear how the current system of defaults and conversions from param value to the value stored in GCTunables would work though. If this is a problem them we could migrate those parameters that are not affected.

For prefs that need additional checks for the set value, it might be best to add some function that reads the pref value and has some extra checks for it. Or sync the prefs at the start of a GC?

Also this would require some way of setting them from the JS shell.

We could add something similar to getPrefValue for setting non-startup prefs.

Severity: -- → N/A
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.