chrome.browsingData.remove is very slow when called with indexedDB and localStorage flags
Categories
(Core :: Storage: IndexedDB, defect, P3)
Tracking
()
People
(Reporter: feedbro.reader, Unassigned)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
4.64 MB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0
Steps to reproduce:
- Create a MV2 WebExtension with browsingData permission
- Call this method in the WebExtension debug console:
console.time("removeOperation");
chrome.browsingData.remove({"since": 0, "originTypes": {"unprotectedWeb": true}}, {"indexedDB": true, "localStorage": true}, function() {
console.timeEnd("removeOperation");
});
Actual results:
For some users, this call takes 30-60 seconds to complete and seemingly freezes the entire browser. But apparently not for all users. It's unknown to us what causes this delay.
The users who reported this problem said that it started a couple of weeks ago. Before that it was working fine.
Expected results:
The call should take no more than a couple of seconds to complete.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Storage: IndexedDB' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
For some users, this call takes 30-60 seconds to complete and seemingly freezes the entire browser. But apparently not for all users. It's unknown to us what causes this delay.
I assume this is related to bug 1671932 - IndexedDB needs a fully initialized quota manager and that might be blocked due to large origin directories (even from unrelated origins). A profile of such an initialization could help to confirm this assumption.
The users who reported this problem said that it started a couple of weeks ago. Before that it was working fine.
That might just be a random effect of having visited some origin that created a huge amount of files in the meantime.
Bug 1804823 appears to be related to this as well.
Updated•2 years ago
|
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Work in under way, removing the perf impact then.
Description
•