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.
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.
(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
Nono, I was saying the opposite — it's totally fair to consider per-profile dbs part of the profile.
Oh, OK. I think the new bug title is still more accurate, unless someone can point out more general cases of Gecko profile corruption.