Large bookmarks cause browser to stop responding for long periods of time. (Similar to bug 46882)

VERIFIED DUPLICATE of bug 52144

Status

SeaMonkey
Bookmarks & History
P3
blocker
VERIFIED DUPLICATE of bug 52144
17 years ago
13 years ago

People

(Reporter: sin, Assigned: Ben Goodger (use ben at mozilla dot org for email))

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (Win98; U)
BuildID:    NS6 Final

It actually doesn't crash the browser, it just appears to. It took me about 30 
minutes before ns6 could import a 250k bookmark file. During that time ns6 
stoped responding. After the import ns6 also took about 10 minutes to load each 
time. 

Reproducible: Always
Steps to Reproduce:
1.import a large bookmark file
2.
3.

Actual Results:  Browser stoped responding for about 30 minutes till bookmark 
import was complete. 
Then each time NS6 was restarted it took about 10 minutes to load. After the 
load if I clicked on my bookmarks there was another 20 minutes of wait time.

Expected Results:  Imported them a lot faster.

I'm not going to use ns6 or mozilla till this bug is fixed. I like quick access 
to my bookmarks.
This is a dupe of bug 52144.

Reporter : This isnĀ“t the Netscape 6 bug reporting database.
If you have problems with Netscape 6 use this URL :
http://home.netscape.com/browsers/6/feedback/problem.html

If you can reproduce a bug on mozilla feel free to open a new bug after you
haves searched at the mozilla bug databse (bugzilla) if this bug is already filled.
If you want to report performance related bugs then please post your used
system. (Pentium III 800 with 128Mb.....)

Thanks



*** This bug has been marked as a duplicate of 52144 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE

Comment 2

17 years ago
Verified dupe.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.