1621868 - Slow/incomplete archive/move a large number of local messages (several thousand pop messages)

Status: UNCONFIRMED

(Thunderbird :: Mail Window Front End, defect)

Description

[neil]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36

Steps to reproduce:

In my Inbox folder, I will select a large number (several thousand) messages, and press A or click Archive.

Actual results:

The bottom of the screen shows the progress ("moving x of y messages to z") and everything seems fine. Then, right at the end, when it looks like it's just about done, it stops. Never gets to "y of y" messages. No error message or anything. It just hangs. Then, I come back sometime later, and I see that the archive process has stopped; but the messages were not moved. Note that the same thing happens if I try to manually move a large number of messages into an archive folder, rather than using the archive function.

Expected results:

Messages should have been moved into the appropriate archive folder, based on year.

Note that if I keep the number of messages to under 1,000, it usually works. However, I have tens of thousands of messages to archive, and doing them 900 at a time is rather tedious.

Account is POP3.

Comment 1

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 2

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 3

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is -- (Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to -- (default, untriaged.)

Comment 4

[Firefox Bug Husbandry Bot]

The severity of these bugs was changed, mistakenly, from normal to S3.

Because these bugs have a priority of --, indicating that they have not been previously triaged, these bugs should be changed to Severity of --.

Comment 5

[Wayne Mery (:wsmwk)]

neil, do you still experience this?

Comment 6

[neil]

(In reply to Wayne Mery (:wsmwk) from comment #5)

neil, do you still experience this?

Well, I no longer have large amounts of messages to archive as I did 5 years ago. I now archive just about every day, so I no longer experience this.

But I'll say that when it was happening, I could safely archive up to about 1800 messages (unlike the 1000 I originally stated). But it would choke if I did too many.

Comment 9

[alexandre.ferrieux]

Wayne, you marked bug 1955237 as a duplicate of this bug, but it is different. There I'm talking about whole-folder moves, while here Neil was doing a selection of a subset of messages, and moving only them.

Comment 10

[Wayne Mery (:wsmwk)]

(In reply to alexandre.ferrieux from comment #9)

Wayne, you marked bug 1955237 as a duplicate of this bug, but it is different. There I'm talking about whole-folder moves, while here Neil was doing a selection of a subset of messages, and moving only them.

I've undone the duplication