If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Reset corrupt or unusable browser database

NEW
Unassigned

Status

()

Firefox for Android
Profile Handling
3 years ago
3 years ago

People

(Reporter: bnicholson, Unassigned)

Tracking

Trunk
All
Android
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
If the user's profile is corrupt, such as from a bad upgrade or I/O error, we should give the option to clear it so the user isn't stuck with an unusable browser.
Do you have examples of particular kinds of corruption?

I've seen corrupt installs, but not corrupt profiles.
(Reporter)

Comment 2

3 years ago
I'm using "profiles" a bit loosely here (borrowed terminology from https://wiki.mozilla.org/Mobile/Roadmap#On_deck) to include browser.db. Good examples would be any of the startupcrash dependencies of bug 975024.
I don't even think that's using it loosely! Sounds fair.
(Reporter)

Comment 4

3 years ago
(In reply to Richard Newman [:rnewman] from comment #3)
> I don't even think that's using it loosely! Sounds fair.

Renaming to make the rnewman happy
Summary: Reset corrupt profiles → Reset corrupt or unusable browser database
Nono, I was saying the opposite — it's totally fair to consider per-profile dbs part of the profile.
(Reporter)

Comment 6

3 years ago
Oh, OK. I think the new bug title is still more accurate, unless someone can point out more general cases of Gecko profile corruption.
You need to log in before you can comment on or make changes to this bug.