Closed
Bug 194836
Opened 22 years ago
Closed 22 years ago
mail will not open. Get error message saying "virtual memory low", must reboot.
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 194835
People
(Reporter: belanger, Assigned: sspitzer)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Build Identifier: Ver. 1.2.1 mail worked fine until I ran "Ad-Aware" software from Lavasoft.com and deleted files in quarantine. Browser works, but when trying to open mail it hangs and will not open. I get an error message "Virtual memory running low". Task manager under processes shows ram being used up rapidly. Must reboot for any other programs to run properly. Removed Mozilla and Ad-Aware then reinstalled Mozilla. Same problem Reproducible: Always Steps to Reproduce: 1.Attempt to open Mozilla Mail& newsgroups 2. 3. Actual Results: No response. Open Task Manager and it says "program not responding". Try to close program then get message "Virtual Memory running low". Must wait about 5 more minutes for it to close the program. Must reboot for other programs to run at normal speed. Expected Results: Opened mail & newsgroups under windows. I'd been using Mozilla Browser and Mail for several weeks w/o problem. This problem did not occur until after I loaded and ran "Ad-Aware" software and deleted quarantined files. Removing the program and reinstalling Mozilla did not remedy the problem. Still exists.
Comment 1•22 years ago
|
||
duplicate submission of bug 194835.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Comment 2•22 years ago
|
||
Reopening in order to resolve as duplicate
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 3•22 years ago
|
||
d *** This bug has been marked as a duplicate of 194835 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•