search

keeleysam / classilla

Automatically exported from code.google.com/p/classilla
0 stars 0 forks source link

Recurrent bookmark bustage #152

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
There are periodic reports from users (who unfortunately did not back up their 
profiles) of bookmark files getting burned in updates. WaMCom apparently does 
this too, so this is a Mozilla bug that was never fixed.

Mitigations (both would be good):
- Back up bookmarks on close. Since most of the problems appear to occur on 
launch, the backup can be salvaged AS LONG AS THE USER DOESN'T CLOSE THE 
BROWSER. To this end, the browser should warn the user when a bookmark reset 
occurs so that the backup can be rescued.

- Reduce exposure (suggested by Mathias). Consolidate writes; do not keep the 
bookmark file open. I don't think caching everything in memory is a good 
solution, but we don't need to have the file continuously open and there is 
some argument that this is exactly what it's doing.

Original issue reported on code.google.com by classi...@floodgap.com on 9 Sep 2010 at 3:50

GoogleCodeExporter commented 9 years ago 
I altered nsProfileDirServiceProvider.cpp to make the bookmarks filehandle 
non-persistent. Let's see if that helps option #2.

Original comment by classi...@floodgap.com on 7 Feb 2011 at 1:02