If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Firefox 1.0 crashes when attempting to open bookmarks imported from Netscape 7.




Bookmarks & History
13 years ago
11 years ago


(Reporter: Andrew Myers, Assigned: Vladimir Vukicevic (BM, do not Cc or Request))



Firefox Tracking Flags

(Not tracked)




13 years ago
The imported bookmarks will list OK when opening the left-hand bookmark pane,
and the bookmark links all appear to work fine.  The crash occurrs ONLY when
attempting to access bookmarks from the Bookmark keyword at the top of the page.
 The behavior is very consistent; i.e., it always crashes at that point.  I
tried uninstalling and reinstalling from scratch.  Installation was flawless. 
Same crash.  Next I will try uninstalling and NOT importing bookmarks from
Netscape and see if that fixes it.  It could be a problem with something
specific in my bookmarks at Netscape, or possibly the fact that in Netscape I
was using my bookmark file as my home page (just a wild guess).

Comment 1

13 years ago
The specific software platform is Mac OS X 10.1.5.  The bookmarks come from
Netscape 7.1 for the Mac.  Hardware is a Mac iBook.


13 years ago
Severity: normal → critical
Keywords: crash

Comment 2

13 years ago
I had no problems with FireFox until I installed version 1.0. The browser
crashes if you attempt to open your bookmarks (they were imported from 0.9) This
behaviour is constant. The program always crashes after clinking on the bookmark
menu. Installing new versions of Firefox (1.1 didn't solve this problem).

Comment 3

13 years ago
Please try to reproduce this with Firefox 1.0.1 or a recent nightly build with
Talkback enabled and submit your crash reports.  To enable Talkback, select
"Custom Install" and make sure to check the box for the Mozilla Quality Feedback
agent.  Thanks.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
You need to log in before you can comment on or make changes to this bug.