165184 - Bookmark corruption with Personal Toolbar folder, bookmark manager crashes

Status: RESOLVED DUPLICATE of bug 109237

(SeaMonkey :: Bookmarks & History, defect)

Description

[Stefan Winterstein]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

Today, Mozilla 1.1 messed up my bookmark file so that bookmark manager crashes
when trying to edit it.


Reproducible: Always

Steps to Reproduce:

Actual Results:  
Opening bookmark manager with the attached bookmark file crashes the browser.

Expected Results:  
Of course:
- Cope with a corrupt bookmark file. 
- Don't mess it up in the first place.

I don't know how the bookmarks became corrupted. The crash first occurred when I
pressed Ctrl-D to bookmark some page, quickly followed by a Ctrl-B to edit,
which crashed the application. I have no idea if this actually caused to the
faulty bookmark file or was a coincidence.

A little investigation showed that the Personal Toolbar folder contains
_another_ Personal Toolbar folder, which is also marked
PERSONAL_TOOLBAR_FOLDER="true".

I'll attach a stripped down version of the corrupt bookmark file.

Comment 1

[Stefan Winterstein]

Attachment: Corrupted bookmark file

This is a stripped down version of my corrupted bookmark file. If needed, I can
also supply the original file (143 KB).

Comment 2

[Alan Arndt]

I just had this happen to me as well.  I am running 1.1 on Windows ME.  I have
no idea how the bookmarks file became corrupted, or really when, though I just
noticed it today.  In my case I could edit my bookmarks, I just couldn't open
the Personal Toolbar folder to edit it, as it had the "recursive" entry it
crashed.  I manually edited the file to delete the three lines associated with
it and all is fine now.

I have a copy of the corrupted bookmarks file if needed.

BTW, the e-mail address for my name is no longer correct, and last I checked I
couldn't change this.  I will check back on the forum.

Comment 3

[Chris Lyon]

It looks like you've somehow stumbled on bug 109237.

*** This bug has been marked as a duplicate of 109237 ***