Closed
Bug 204034
Opened 21 years ago
Closed 21 years ago
Lock at Startup with 1.4a
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 195600
People
(Reporter: salva, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 When I start a fresh install of Mozilla 1.4a on WinXP SP1, it is blocked with 100% CPU. The only way to make it run is to change the priority of the mozilla.exe process to high or to kill it. Verion 1.3 is O.K. . Reproducible: Always Steps to Reproduce: 1. Install 1.4a 2. Start Mozilla 3. Actual Results: Lock of Mozilla during startup Expected Results: Start much more faster without using 100%
Comment 1•21 years ago
|
||
Did you overwrite your previous mozilla installation ? If so, this bug is invalid.
Comment 1 is correct. If you have a previous Mozilla installation you'll need to uninstall it AND manually clear out the Mozilla folder. If you haven't done that, this is a dupe from bug 195600. You can read the discussion in bug 200623 for more information. Marking it as a dupe. If you think you see another issue, reopen this bug. *** This bug has been marked as a duplicate of 195600 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
This bug should be re-opened. Firstly, this bug reports Moz locking up sucking ~100% CPU, whereas bug 195600 is about Moz *crashing*; not the same thing IMO. Secondly, I can reproduce this reliably both in Moz 1.4 with a new profile and Firebird 0.6 with a fresh install. I *always* zap mozilla.org\Mozilla between installs and Firebird has been installed for the first time ever on this machine. The cause is an empty, apart from the comments, prefs.js If I copy a prefs.js from another profile both Moz and FB start fine. Delete the contents of prefs.js and the problem returns. As well as sucking ~100% CPU, both display "Resolving www.mozilla.org" in the status bar and the memory usage continues to rise.
OK, I've found the cause, or perhaps more accurately, a fix/workround. If this line is added to the empty prefs.js file both Moz and Firebird startup fine user_pref("browser.bookmarks.added_static_root", true);
Bah! forget it. What I'm seeing is bug 201381. Hadn't associated the problem with IE Favourites.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•