[Windows] Profile not fully deleted from local directory
Categories
(Toolkit :: Startup and Profile System, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox133 | --- | unaffected |
| firefox134 | --- | disabled |
| firefox135 | --- | disabled |
| firefox137 | --- | disabled |
| firefox138 | --- | verified |
People
(Reporter: sbadau, Assigned: jhirsch)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-profile-management])
Attachments
(1 file)
Found in
- Nightly 135.0a1
Affected versions
- Nightly 135.0a1
- Firefox 134.0b2
Tested platforms
- Affected platforms: Windows 10, Windows 11
- Unaffected platforms: macOS 15
Preconditions
- Set the pref "browser.profiles.enabled" to "true" in about:config and create one profile (Profile 1).
Steps to reproduce
- Launch Profile 1, open the Profiles panel and click on Edit.
- Click on the Delete button.
- On the about:deleteprofile page, click the Delete button.
- Return to the Profiles panel and check the profiles list.
- Navigate to AppData\Roaming\Mozilla\Firefox\Profiles and inspect the profiles list.
Expected result
- Profile 1 should be deleted from both the Profiles panel from Firefox and the local directory.
Actual result
- Profile 1 is not fully deleted from the local profile directory.
Regression range
- This is not a regression, it's introduced with the Profile Switching feature.
Additional notes
- Profile 1 directory still contains a 'saved-telemetry-pings' folder and a parent.lock file.
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
I'm not sure if these last few files can actually be deleted. Thoughts?
Comment 3•1 year ago
|
||
The severity field is not set for this bug.
:mossop, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
I'm no longer able to reproduce this bug on Windows 11. Could you verify that it's still reproducible?
| Reporter | ||
Comment 5•1 year ago
|
||
(In reply to Jared Hirsch [:jhirsch] (he/him) (Needinfo please) from comment #4)
I'm no longer able to reproduce this bug on Windows 11. Could you verify that it's still reproducible?
I can still reproduce this issue. I tried using the latest Nightly 137.0a1 (Build ID: 20250220214610). The profile folder, which contains a "saved-telemetry-pings" folder and a parent.lock file, is not deleted from AppData\Roaming\Mozilla\Firefox\Profiles.
I also checked AppData\Local\Mozilla\Firefox\Profiles, and indeed, the profile folder is entirely deleted from this location.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 6•1 year ago
|
||
| Assignee | ||
Comment 7•1 year ago
|
||
Reading back through the changes in D222058, I was reminded that we don't retry deletion of leftover files because of a now-closed bug.
For an initial attempt, trying to just add some retries. Building this on windows now, will try it out next week.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 9•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
| Reporter | ||
Comment 10•1 year ago
•
|
||
Verified as fixed using Firefox 138.0b1 and the latest Nightly 139.0a1 on Windows 11 - the folder of the deleted profile is no longer present in the Profiles folder.
Updated•1 year ago
|
Description
•