Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

How do I reconstruct a profile?

  • 26 respuestas
  • 1 tiene este problema
  • 1 visita
  • Última respuesta de firefox179

more options

My profile appears to be corrupted. Newly created bookmarks disappear when the session is ended and new one is started. If I create a new profile and copy the contents of the old one, the problems come with it. I've tried removing add-ons, but none seem to be the cause. Safe mode works, but that's not a long-term solution. I've reinstalled FF, but copying the profile brings the problems with it.

My latest attempt is to create a new profile and import bookmarks, creating a new places.sqlite file. I copied a variety of other files (prefs.js, extentions*, key3.db, key4.db) and so far everything still works.

There's one issue with extensions.json and extensions.sqlite. These point to the extensions directory of the old, corrupted profile. This works, but obviously is not desirable. It's easy to do a find/replace on the .json file, but without changing the the .sqlite file this breaks extensions. Fixing the .sqlite file is harder (at least for me), but do-able. Is that the right solution?

Or is there a better way to reconstruct a corrupted profile?

My profile appears to be corrupted. Newly created bookmarks disappear when the session is ended and new one is started. If I create a new profile and copy the contents of the old one, the problems come with it. I've tried removing add-ons, but none seem to be the cause. Safe mode works, but that's not a long-term solution. I've reinstalled FF, but copying the profile brings the problems with it. My latest attempt is to create a new profile and import bookmarks, creating a new places.sqlite file. I copied a variety of other files (prefs.js, extentions*, key3.db, key4.db) and so far everything still works. There's one issue with extensions.json and extensions.sqlite. These point to the extensions directory of the old, corrupted profile. This works, but obviously is not desirable. It's easy to do a find/replace on the .json file, but without changing the the .sqlite file this breaks extensions. Fixing the .sqlite file is harder (at least for me), but do-able. Is that the right solution? Or is there a better way to reconstruct a corrupted profile?

Todas las respuestas (6)

more options

Until they send out an update that fixes the bug . . . . .

more options

places.sqlite shouldn't get corrupted that often or even once under normal conditions. Files getting corrupted usually happens if other software is involved and keeps a handle on specific files or other (cleanup) software tries to make changes to files causing this file to get corrupted.

more options

FredMcD said

Until they send out an update that fixes the bug . . . . .

Is this a known problem awaiting a bug fix, or does the bug still need to be identified?

more options

cor-el said

places.sqlite shouldn't get corrupted that often or even once under normal conditions. Files getting corrupted usually happens if other software is involved and keeps a handle on specific files or other (cleanup) software tries to make changes to files causing this file to get corrupted.

I am running no cleanup software. A cloud backup program runs during a fixed window overnight, but I've seen this problem occur in a span that doesn't involve that time window. Same for virus scanner (MSE).

If I'm reading Process Explorer correctly, there appears to be four distinct handles associated with places.sqlite, all connected to the same firefox process ID. One handle has 6 references, the others have 1 each.

No other process holds a handle to places.sqlite

more options

firefox179 said

Is this a known problem awaiting a bug fix, or does the bug still need to be identified?

FredMcD said

Bug 1326309 - Opened 3 years ago
more options

FredMcD said

firefox179 said
Is this a known problem awaiting a bug fix, or does the bug still need to be identified?

FredMcD said

Bug 1326309 - Opened 3 years ago

Since I wasn't using sync I didn't realize that the earlier report referenced my case as well, but I see you've added this event to that report.

I guess I shouldn't hold my breath on a three year old bug with fix-optional status suddenly jumping to the top of the queue :-)

Again, thanks for your attention to this issue.

  1. 1
  2. 2