(In reply to Markus Stange [:mstange] from comment #44) > Andrew, what are the next steps here? Unfortunately, we don't have resources to staff async init (bug 1671932) until H1. Please direct any staffing questions to manager people. I've marked bug 1953860 as fixed and downgraded this bug from P1 to P2 since the situation is massively improved but is still something we plan to address. There is a mechanism that conservatively "archives" old origins that could instead be changed to purge them if someone has cycles to take a look at that and which could potentially also be augmented to handle the 0-usage edge cases alluded to in comment 38. They'd want to look at the code around [dom.quotaManager.longQuotaInfoLoadTimeThresholdMs](https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/modules/libpref/init/StaticPrefList.yaml#3957-3962) and [dom.quotaManager.unaccessedForLongTimeThresholdSec](https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/modules/libpref/init/StaticPrefList.yaml#3881-3890), specifically [this code goes and performs the archiving](https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/dom/quota/ActorsParent.cpp#3115-3120). But we wouldn't want to archive things since that just bloats the profile and creates privacy problems as the functionality currently exists.
Bug 1903530 Comment 45 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Markus Stange [:mstange] from comment #44) > Andrew, what are the next steps here? Unfortunately, we don't have resources to staff async init (bug 1671932) until H1. Please direct any staffing questions to manager people. I've marked bug 1953860 as fixed and downgraded this bug from P1 to P2 since the situation is massively improved but is still something we plan to address further. There is a mechanism that conservatively "archives" old origins that could instead be changed to purge them if someone has cycles to take a look at that and which could potentially also be augmented to handle the 0-usage edge cases alluded to in comment 38. They'd want to look at the code around [dom.quotaManager.longQuotaInfoLoadTimeThresholdMs](https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/modules/libpref/init/StaticPrefList.yaml#3957-3962) and [dom.quotaManager.unaccessedForLongTimeThresholdSec](https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/modules/libpref/init/StaticPrefList.yaml#3881-3890), specifically [this code goes and performs the archiving](https://searchfox.org/firefox-main/rev/856a307913c2b73765b4e88d32cf15ed05549cae/dom/quota/ActorsParent.cpp#3115-3120). But we wouldn't want to archive things since that just bloats the profile and creates privacy problems as the functionality currently exists.