837620 - Folder Compact on Thunderbird startup, or switching to newsgroup, results in error "Operation is in progress"

Status: NEW

(Thunderbird :: General, defect)

Description

[arky [:arky]]

When you switch to one of NEWS: folders when Thunderbird nightly begins. This modal dialog pops up 

" The folder 'All Mail' cannot be compacted because another operation is in progress. Please try again later."

Comment 1

[Wayne Mery (:wsmwk)]

(In reply to arky [:arky] from comment #0)
> When you switch to one of NEWS: folders when Thunderbird nightly begins.
> This modal dialog pops up 
>
> " The folder 'All Mail' cannot be compacted because another operation is in
> progress. Please try again later."

the compact activity is normal. The "All Mail" part points to bug 816327

Comment 2

[Wayne Mery (:wsmwk)]

Arky, do you still see this issue?

Comment 3

[Wayne Mery (:wsmwk)]

Steve, do you use both newsgroups and gmail?

worth noting, bug 1260698 is likely the main cause for compact happening so often when accessing a newsgroup.  Because for several years imap users' folders were not being automatically compacted. 

(Unfortunately no response from reporter Arky.)

Comment 4

[sfhowes]

I have a gmail account set up in a profile but only for testing.  My regular profile has 3 IMAP accounts and a newsgroup, but I've never seen the type of behaviour reported in this bug.

Comment 5

[João Carlos Mendes Luís]

"Operation is in progress" bug is not exclusive for gmail nor to Thunderbird startup.  It usually happens to me after I mark many messages for deletion.  Unfortunately is not 100% repeatable.  Must be some race or missing lock.

Comment 6

[doug2]

Running beta TBird 67.0b3 and other recent betas, this compaction process (and "Operation Failed message) happens very often when I "wake up" TBird to work on mail. Compaction takes a long time and is frustrating since TBird is not available. More importantly, the compaction is almost always followed by bug #1362483 "Gloda stuck in a loop ..." In other words, compaction (possibly with other sub-processes involved) is leaving the database in an unstable state. FYI, Gloda stuck in loop runs cpu usage up until editing is nearly impossible.

Comment 7

[Nils]

This bug is definitely still preset in 115.6.0
I get it on startup when it tries to compact mails while at the same time refreshing over a hundred folders from an IMAP server. TB should not internally conflict itself (should lock some operations maybe?) and even if it does, the warning is not helpful coming dozens of times as the user can do nothing about it.