Telemetry is completely OFF, but there are thousands files in datareporting\archived
Categories
(Toolkit :: Telemetry, defect)
Tracking
()
People
(Reporter: mowod66703, Unassigned)
References
Details
Attachments
(1 file)
|
352.94 KB,
image/png
|
Details |
datareporting in firefox compared to watefox
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:152.0) Gecko/20100101 Firefox/152.0
Steps to reproduce:
Telemetry is disabled in FF, but thousands of files in profile folder "datareporting\archived" are still created
If telemetry is OFF - dont create that files! No need to make additional "garbage"
Actual results:
Files are still written in "datareporting\archived" while ALL telemetry is off
Expected results:
Files should not be created in "datareporting\archived" folder when telemetry is off (no need to make irrelevant disk writes)
|
||
Comment 1•3 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Telemetry' component, but is not confident enough to move the bug to that component.
|
||
Updated•3 months ago
|
|
||
Comment 2•2 months ago
|
||
Firstly and most importantly: these aren't uploaded if you have telemetry disabled. They are a local archive only.
I believe the fact that we still keep an archive of some of the data is for historic reasons. The legacy telemetry system's history includes a time where it was used to record diagnostic data locally so that users could use it to diagnose problems they might be experiencing (like slow startup or bad performance). That part was never fully taken out.
Luckily, this behaviour will soon be removed. We're in the process of replacing Legacy Telemetry with a different collection library called Glean. Glean doesn't have an archive at all, and if data upload is disabled it just stops recording data (rather than writing it down in case a curious user would like to inspect it locally). By the end of 2026 we hope to have turned off and removed Legacy Telemetry from Firefox Desktop, so by then at the latest we should be rid of this unexpected behaviour.
For now, though, I would understand if you're not content with the behaviour. If you'd rather that the archive not be updated with new pings that will never be uploaded, you can turn off the Telemetry Archive by opening about:config and setting toolkit.telemetry.archive.enabled to false: this disables the archiving of pings whether you have data upload enabled or disabled. If you don't mind the behaviour now that it's been explained, you can feel free to leave it to do its own thing -- it's a self-limiting system, so it won't take more than 120MB of disk space and won't store any pings older than 60 days.
Does that resolve your issue? If so, I will close this bug.
This is not about "sending anything" or disk space usage, it is more about stop rush disk to write redundant information
Yes, FF gathers only latest 2 month of data and size is not large, but it writes many tiny files every day many times.
It is all about "decrease unnecessary disk writes" if telemetry is off.
Many programs do this and every software do this in small amounts, but all together is became mess of logs written while not being necessary
If FF will move to new telemetry system which will not do unnecessary disk writes soon then this bug can be closed
|
||
Comment 4•2 months ago
|
||
|
||
Comment 5•2 months ago
|
||
(In reply to esprigde from comment #3)
This is not about "sending anything" or disk space usage, it is more about stop rush disk to write redundant information
Yes, FF gathers only latest 2 month of data and size is not large, but it writes many tiny files every day many times.
It is all about "decrease unnecessary disk writes" if telemetry is off.Many programs do this and every software do this in small amounts, but all together is became mess of logs written while not being necessary
If FF will move to new telemetry system which will not do unnecessary disk writes soon then this bug can be closed
It depends if "hopefully by the end of 2026" is considered "soon" for you, but yes: we are moving that way, so I will marked this resolved. If that's not "soon", you can follow the instructions in comment #2 to turn off the archive on your own timescale.
Description
•