Closed Bug 387957 Opened 19 years ago Closed 18 years ago

McShield 99% of CPU when read/send new email or changing folders

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jerry.klink, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1) Build Identifier: 2.0.0.4 I was demo-ing Thunderbird 2.0.0.4 as an alternative to Outlook. I'm VERY impressed with one exception. Our company uses McAfee 8.0 Enterprise on all PC's, the settings are locked I can't change them. One every new email, or send or even changing to a different folder, McShield sky-rockets to 99% and stays there for 7-20 secs rendering my PC unusable. As much as i like the software, I can't use it in that present state. A friend has advised that i try the older 1.5.0.12 ver as a workaround. I can report that so far I don't seem to notice the same issues. I'm not sure what may have changed between the two versions, if that can be fixed and i can maintain the A/V scan of each e-mail, I can upgrade to the newer 2.0.0.4 ver. If not, I'm forced back to Outlook. Reproducible: Always Steps to Reproduce: 1. Try and open a new email in ver 2.0.0.4 2. Try and send an new or reply to an email in ver 2.0.0.4 3. Change to a different folder (all email moved by filters from inbox to a specified folder - inbox always left empty) Actual Results: As described above Expected Results: I can see/understand a temp slowdown as new emails are being scanned on receipt, but not why emails would need re-scanning when switching from one folder to another Changed the view from folder one to folder two without the slowdowns / freeze
Version: unspecified → 2.0
Jerry, classic symptom of AV not playing nice with or configured for the application http://kb.mozillazine.org/Antivirus_software http://kb.mozillazine.org/Thunderbird_2.0_installation_issues fixed ?
no response, so => incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.