Open Bug 1753110 Opened 2 years ago Updated 8 months ago

Lingering tmpaddon files in the OS temporary folder when an add-on has an update

Categories

(Toolkit :: Add-ons Manager, defect, P3)

defect

Tracking

()

People

(Reporter: robwu, Unassigned)

References

Details

When an add-on has an update, it is downloaded to a temporary location, and the update may automatically be installed, or cancelled/not processed (if it has a permission prompt).

The tmpaddon* file is created at https://searchfox.org/mozilla-central/rev/b70bc09685763c44a8e56e4e04cb741fa020701a/toolkit/mozapps/extensions/internal/XPIInstall.jsm#4055-4061

And the file should ultimately be deleted after the update notification has been handled by https://searchfox.org/mozilla-central/rev/b70bc09685763c44a8e56e4e04cb741fa020701a/toolkit/mozapps/extensions/internal/XPIInstall.jsm#2978-2979, specifically by an onUpdateAvailable listener (called from here).

Because this file is not explicitly deleted, tmpaddon files may accumulate in the tmp dir.

Blocks: 1670503
Severity: -- → S4
Priority: -- → P3
See Also: → 1853443
You need to log in before you can comment on or make changes to this bug.