378360 - Avast! antivirus makes it slow to send and delete mails

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: Avast AV, defect)

Description

[Snakefoot]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.4pre) Gecko/20070421 BonEcho/2.0.0.4pre
Build Identifier: version 2.0.0.0 (20070326)

Have an pop3 Inbox with a size of 70 MByte, and when getting emails or deleting emails, then the CPU goes 100% for a few seconds on an Athlon XP 3000.

When disabling Avast! then this behavior disappears, so have now excluded my profile folder from the Avast! scanning to get rid of this problem.

Would be nice if Avast! and Thunderbird could play together nicely, as I don't have the problem in Outlook Express with the Inbox of the same size.

Reproducible: Always

Steps to Reproduce:
1. Install Avast! 4.7
2. Select a single mail in a large Inbox
2. Press delete

Actual Results:  
100 pct. CPU usage for 2-3 seconds.

Expected Results:  
Delete mail without high CPU usage

Comment 1

[Carsten Book [:Tomcat]]

(In reply to comment #0)
> When disabling Avast! then this behavior disappears, so have now excluded my
> profile folder from the Avast! scanning to get rid of this problem.

I guess this is something related to the Avast Antivirus Scanner and a Thunderbird Bug. Maybe you should report this to Anvil (Avast Vendor). There is a support forum under http://forum.avast.com/

Marking this invalid, since send an delete works fine without avast.

Comment 2

[timeless]

We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.

Comment 3

[Benjamin Smedberg]

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.