287400 - Avast virusscan makes TB slow

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: Avast AV, defect)

Description

[WillyB]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; nl-NL; rv:1.7.6) Gecko/20050318 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl-NL; rv:1.7.6) Gecko/20050318 Firefox/1.0.2


Scets of my tb-client:
Migrated from outlook with some problems, but all of these have been fixed.
Have been using thunderbird for quite some time now.
Using master password
Got a lot of maps in a separate (not inbox) map

Problem:
Everything in the main window (like inbox, but all maps also if i create a new
one) takes a lot of time (showing, deleting messages). 

(problem stays after upgrading to 1.02)

Reproducible: Always

Steps to Reproduce:
1. Open tb.
2. Click on a message (that has not been opend yet!)
 .... wait 5 secs..... (terrible!)
3. Click on delete

If i open a already opend message it's fast (deleting is still slow)
Actual Results:  
Slow, have to wait a couple of seconds before tb goes on. (but it does what i
tell it do do)

Expected Results:  
Be fast (just like on all other pc's :)

It gives no error. But CPU power is always 100% for very short time when opening
a message or deleting a message.

Comment 1

[David :Bienvenu]

do you have an anti-virus program installed? If so, try disabling it or
upgrading it to see if that's the cause of the slow down... What's the speed of
your CPU, and your network connection?

Comment 2

[WillyB]

Problem stops when disabling AVAST Home virusscan (winXP). Thnx. But it's a
workaround.
So i changed the title to "Avast virusscan makes TB slow".

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 5

[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 6

[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.