User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20170802111520 Steps to reproduce: Tap the Menu button, select Settings, scroll down to the Privacy & Security section and choose Clear private data. Confirm. Actual results: It takes about 7 seconds on my octa-core 1.3GHz Cortex-A53 smartphone until the Success message is being displayed, even if the browser cache is empty. Expected results: The clearing process should finish almost instantly (as it was in past versions). Unfortunately I can't name an exact version when this behaviour was introduced, but it came from one version to another (not related to a slowed down file system) and it's that slow since at least about half a year.
We might or might not be able speed up data clearing for real, but what you're seeing is most probably the effect of bug 1343995, which was fixed on Release with Firefox 53, which came out mid-April and would the time scale you've given. Because of a logic error, we didn't actually wait for the data clearing to finish (and some issues are probably lurking even today, but those affect only individual data categories, not everything like bug 1343995). That is of course a nice - if unintentional - way of making data clearing appear to be faster than it actually is, but it is not a good idea during shutdown, because it means we proceed with the shutdown process before all data clearing has actually finished.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → Android
Hardware: Unspecified → All
Summary: Clearing private data takes several seconds on Android → Investigate potential for speeding up clearing of private data
Hi Joe Please help advise.
FYI, there is telemetry data available for this - look for the various FX_SANITIZE histograms.
8 months ago
Priority: -- → P3
It seems like the duration for the clearing process has increased again in FF for Android 60. Is there no chance to fix this?
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.