Closed Bug 81844 Opened 24 years ago Closed 23 years ago

Mozilla hangs during startup with 100% CPU usage

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: angeli, Assigned: asa)

References

Details

I cannot start the latest nightly builds on my PC. They hang during startup with 100% CPU usage. The latest build which is working correctly is 2001051813. In the console the last thing that is written is the registration of the nullplugin. The browser window stays sometimes blank and sometimes some parts of the GUI are displayed. I tried to delete the .mozilla directory to force it to create a new account but it had no effect. Additionally I tried to delete the cache directory, also with no effect. I am running SuSE Linux 7.1 with kernel 2.4.4.
*** Bug 81845 has been marked as a duplicate of this bug. ***
WFM Linux tip cvs today. Two other people are reporting they work as well (jag, cls). Reporter: can you confirm that you are blowing away the old installation dirs? For example, if you install into /usr/local/mozilla, please rm -rf /usr/local/mozilla and then install, fresh.
I am deleting the whole mozilla directory with rm -r and making a tar xzf of the new archive. So the only thing that stays is the .mozilla profile directory. I haven't tried CVS so far.
Similar things happen on a RH/6.2 with 2001051921. Mozilla opens its window, but when a request is being made, cpu usage goes to ~99% and it hangs. When removing .mozilla, it successfully converts old profile, and same thing happens afterwards. I also install the jre.xpi with every new nightly, and mozilla seems to successfully register all plugins (including jre) during startup.
Those who see the hang: Are your preferences set to load a homepage on startup?
Yes, I am loading www.google.com at startup.
But that shouldn't make a difference as it also hangs with a new profile.
Nope, my profile does not load a page on startup.
A new profile has mozilla.org as homepage, doesn't it. I wonder if this all is related to the recent cache bugs. Hang is reported in bug 81799, crash in bug 81764.
My profile is migrated from ns4.77, which does not have a homepage.
Seems to be many funny problems going on. I just created a new profile from scratch (as root) and indeed got a hang. The dir "NewCache" was not created. First after a "killall mozilla-bin" and restart, the NewCache dir was created and mozilla ran. Didn't see excessive CPU usage though.
Tried this, too: - remove .mozilla - start mozilla, it migrates ns4 profile - exit without doing anything - restart mozilla - try a url from bookmarks - mozilla goes a little bit further than before (ie, host lookup + redit + new host lookup) - than, mozilla hangs, with cpu @ 98% The site I visited is www.mtnsms.com, which immediately redirects to one of wwwX.mtnsms.com. I can see the lookups, which means mozilla is connecting, gets the redirect, tries again and hangs. BTW, don't know if it's relevant, but .mozilla directory only contains appreg, and none of the files it used to contain earlier.
Marking as NEW, as other users experience similar problems.
Appears to be the same in W2K. Tries to resolve host to home page (www.yahoo.com) with one of yesterday's builds (21 May 2001) and freezes (menus, icons don't work.) Haven't installed a clean copy, nor tried any of the other steps gone over in this bug's activity report. SQ
btw, yesterday = 20 May 2001 :) SQ Still doesn't work with build 2001052104 in W2K.
I'm getting what might be the same thing Red Hat 7.0 with a May 21 build. If i try to start Mozilla from a console, the last thing i see is the registration of the 0 plugin. However, if my CPU is hogged, it's only momentarily. No gui widget ever even appears, maybe because i have a slow machine.
Okay, I just downloaded the latest nightly build (2001052121) for Linux and this one worked for me. What a relieve. ;o)
Using 2001052121 to send this, which means it's wfm
Now works for me in W2K - build 2001052204 SQ
wfm per reporter's and others' comments. thanks for the follow-up.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Still doesn't work for me with a Linux May 23 build.
Okay, it even works for me now.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.