192398 - On startup, splash screen appears, CPU pegs at 100%, and mozilla hangs while allocating 2MB of ram/second

Status: VERIFIED DUPLICATE of bug 169777

(SeaMonkey :: General, defect)

Description

[Brian Kasper]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.3a/mozilla-win32-1.3a-installer.exe

I've been using the 1.3 alpha release for a while now without problems.  This
morning when I started the browser, the splash screen appeared but the browser
never started (the splash screen continued to be displayed).  When I checked
Task Manager, the mozilla.exe process was using 100% of my CPU and its memory
usage was increasing by roughly 2 megabytes per second!  I finally killed the
process when it was using 180 megabytes of RAM.

I don't know if this has any bearing on the problem, but I ran "Windows Update"
yesterday and got all of Microsoft's "critical" updates, including the latest
version of IE6 and all IE service packs.  I also installed Windows Media Player
version 9.

I uninstalled and reinstalled Mozilla, and the problem still occured.  It also
happened if I tried to launch the mail client.

Reproducible: Always

Steps to Reproduce:
1. Start Mozilla
2. Look at cool splash screen while CPU usage goes to 100% and memory usage climbs
3. Sigh sadly and kill mozilla proces

Actual Results:  
Mozilla hangs at splash screen with 100% CPU usage and and a memory footprint
that increases at 2MB/second without bound

Expected Results:  
Mozilla should have launched the browser component.

I'm using the classic theme on Windows 2000 Service Pack 3 with all the latest
updates (including IE 6.0.2800.1106 and Windows Media Player 9.00.00.2980) and
the latest SUN Java install.

Comment 1

[Frederic Bezies]

I had such a problem so days ago.

Try removing xul.mfl and your mimetypes.rdf file from your profile.

Did you still see this bug ?

Comment 2

[Frederic Bezies]

Had a mail from reporter saying me that removing xul.mfl was the answer.

So, this is a duplicate (again !) of 169777

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

Comment 3

[Torben]

.