Closed Bug 299119 Opened 20 years ago Closed 20 years ago

Downloading mail with Mozilla 1.7.8 breaks internet connection & goes 100% CPU

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: massimo_main, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 When I start MailNews in Mozilla 1.7.8 it starts downloading mail from POP3 but instead instantly breaks internet connection and waits mail forever (waited for half an hour last time: no mail - no error message - nothing, just still waiting connection with POP3 server). At the same time, the program MOZILLA.EXE in task manager gets 100% CPU (the first in the list with same name, the others gets normal - about 0% - CPU usage. But when I shut down the 100% one, the next takes immediately 100% CPU itself): I have to shut down every opened Mozilla app/window to regain normal CPU usage ratio. During this time, Mozilla is still responding to commands (menus are functional) but even after I get up connection again the browser fails loading webpages (and still NO email, ofcourse). I have to shut down all and every browser/mail window and relaunch before getting things to work again. PS. my POP3 accounts are OK and does have mail, I tested it via webmail interface. Reproducible: Always Steps to Reproduce: 1.Open browser. 2.Launch Mail & Newsgroups from quicklaunch bar in the browser status bar. Actual Results: internet connection gone line down - Mozilla gets 100% CPU - unable to browse any site or download any mail after reconnection. Expected Results: polling POP3 accolunts, downloading mail. No crash reported
Tweaking around I came to the solution: were the IMON and EMON features of my NOD32 antivirus which were conflicting with another program for reading webmail from mozilla (liberopopsd): I disabled IMON and EMON and now everything works fine. Sorry for the false report :(
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.