Closed Bug 1917355 Opened 9 months ago Closed 8 months ago

Very slow to delete messages, and slow to load messages with Microsoft Defender

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 128
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: gspatz1, Unassigned)

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0

Steps to reproduce:

I added Thunderbird as a folder to my list of "exclusions" in MS Defender virus and threat protection. I took it off the list. I put it back on. I took it off. Restarted TB multiple times.

Actual results:

At first, TB returned to normal and I was able to load and delete my email messages like I'd always done in the past. Less than a second between each message. But after a few days, the problem returned. I click on a message to delete it and it hangs there for 5-10 seconds before deleting. This turns the daily task of deleting emails into a much longer and pointless task.

Expected results:

I would like my messages to load and delete as quickly as they used to in older iterations of TB.

What is your full version number?

Keywords: perf

128.2.0esr

I changed the way I added TB as an exception to my virus protection, including the user pathway, and that seems to have helped. Though I wonder how long that will last, and how safe it is excluding TB from virus protection.

Thanks for the update.

How many messages in the Trash folder?
And how many messages in the folder from which you are deleting?

Flags: needinfo?(gspatz1)
Summary: The new update of Thunderbird is very slow to delete messages, and slow to load messages → Very slow to delete messages, and slow to load messages with Microsoft Defender

I don't think there's much we can do here. One option, apart from excluding the profile from constant virus scanning, is using maildir.

Status: UNCONFIRMED → RESOLVED
Closed: 8 months ago
Resolution: --- → INVALID
Flags: needinfo?(gspatz1)
You need to log in before you can comment on or make changes to this bug.