Closed Bug 346313 Opened 18 years ago Closed 18 years ago

hundreds of backup bookmark files in profile

Categories

(Firefox :: Bookmarks & History, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 294584

People

(Reporter: jnoreiko, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.5) Gecko/20060723 Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.5) Gecko/20060723 Firefox/1.5.0.5

In my profile folder I have several hundred files called:

Library/Application\ Support/Firefox/Profiles/default.hmb/bookmarks-xxx.html

where xxx is a number from 1 to 347.
The last modified date of each file matches its creation date.
The first one was created 25 May 2005. The most recent today.
Together they take up about 150MB.

(Is it safe to delete them, btw?)


Reproducible: Always
Using any extensions? The only backups we create are in bookmarkbackups/, and those should only date back a week.
(In reply to comment #1)
> Using any extensions? The only backups we create are in bookmarkbackups/, and
> those should only date back a week.

I was, but I have removed all extensions except Talkback (1.5.0.5) and 'View Rendered Source Chart' which Firefox has disabled because of incompatibility (and this means the uninstall button is greyed out) -- the problem still occurs.

I have observed that the new bookmark file is created when I quit firefox.
Each one is an exact copy of my bookmarks.html file in the same folder.
What is the browser.bookmarks.max_backups preference set to?
I don't see that preference listed in about:config.
Starting with browser.bookmarks, there is only:

browser.bookmarks.added_static_root
browser.bookmarks.sort.direction
browser.bookmarks.sort.resource

Filtering on 'backup' or 'max' gives no results.

*** This bug has been marked as a duplicate of 294584 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.