Not able to remove Local storage data with 'Clear Browsing Data' extension
Categories
(WebExtensions :: Storage, defect, P5)
Tracking
(Not tracked)
People
(Reporter: mozi, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
I use the Clear Browsing Data extension by Armin Sebastian.
https://addons.mozilla.org/en-US/firefox/addon/clear-browsing-data/
With this extension I am able to remove cookies and cache etc. with one single mouseclick. The extension supports several "Data Types" which can be removed. I am not able to remove the "Local storage data". The other Data Types are not a problem.
I have reported this bug to the owner of the extension. He advised me to report this bug here in bugzilla. Check here the issue on github: https://github.com/dessant/clear-browsing-data/issues/23
I did some tests with several other profiles. I do not experience the problem with a fresh profile, but with other older profiles I am able to reproduce the problem. So the problem is probably related to older profiles.
I hope this can be solved without replacing my Firefox profile.
Actual results:
When I try to clear the Local Storage Data with the extension, the Browserconsole gives this error:
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.hostPort] ext-browsingData.js:192
Expected results:
Firefox should clear the Local Storage Data when I hit the extension-button.
When I use Ctrl-Shift-Delete in the browser and select "Offline Website Data" the remove is succesfull. (I think "Offline Website Data" is the same as "Local Storage Data"? Correct me if I'm wrong).
|
||
Comment 1•5 years ago
|
||
The priority flag is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Comment 2•5 years ago
|
||
This sounds like a bug in the extension, have you reported it to them?
I have reported this bug to the owner of the extension. He advised me to report this bug here in bugzilla. Check here the issue on github: https://github.com/dessant/clear-browsing-data/issues/23
The extension is a thin wrapper around browsingData, and the NS_ERROR_FAILURE error happens only with browsing data persisted in older profiles. The API function call does not seem to return after the error, so far this appears to be a browser bug.
Mozi, you could share the Firefox version you used to create the older profile for easier triaging.
The Firefox version at that moment was probably Firefox 62, based on the installation date of my OS. I am now running Firefox 71.0.
Today I tried again with this extension to remove the Local Storage and it worked without any problems. I don't know what has changed or what this problem solved, but it seems to be solved now!
I'm also using the Clear Browsing Data extension. It won't clear local storage on my working release (75.0) profile, nor will it on Beta, Dev, or Nightly. I just created a new release profile and immediately went to several sites to populate cookies and storage. After clearing cookies and storage with the extension, cookies were deleted; storaage was not. In fact, I have tried several similar extensions and in all cases, storage will not delete. I'm not quite sure how to determine if indexeddb is being deleted.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
(In reply to Ed from comment #7)
I'm also using the Clear Browsing Data extension. It won't clear local storage on my working release (75.0) profile, nor will it on Beta, Dev, or Nightly. I just created a new release profile and immediately went to several sites to populate cookies and storage. After clearing cookies and storage with the extension, cookies were deleted; storaage was not. In fact, I have tried several similar extensions and in all cases, storage will not delete. I'm not quite sure how to determine if indexeddb is being deleted.
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0
Your issue seems to be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1526246.
|
||
Updated•2 years ago
|
|
||
Comment 10•17 days ago
|
||
This specific error was triggered with this version of the code: https://searchfox.org/mozilla-central/rev/90fac8fa22c1a213704999fa63f7423fc6d3a11a/browser/components/extensions/parent/ext-browsingData.js#192
The error is happening because not all URLs support hostPort.
These days, there is a check before hostPort is accessed, at https://searchfox.org/mozilla-central/rev/18bfd136df7f2fe618d8105549cccebb75ce92f5/toolkit/components/extensions/parent/ext-browsingData.js#153-161
Upon tracing the history, I found that this was fixed by this change: https://searchfox.org/mozilla-central/diff/7fb1f49727afc161db9032791e2b93e9c507ed8d/browser/components/extensions/parent/ext-browsingData.js#193-201
Which makes this a duplicate of bug 1575891 (which was already fixed within weeks after this report was filed).
|
|
||
Updated•17 days ago
|
Description
•