509128 - Auto Compacting folders makes compose and read windows lose functionality, forced to close window

Status: RESOLVED INCOMPLETE

(Thunderbird :: Message Reader UI, defect)

Description

[Emerson Prado]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; pt-BR; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
Build Identifier: 2.0.0.22 (20090605)

If I'm reading or writing a message while Thunderbird is compacting folders, no matter what comes first, the read/compose window stops working. That is:
In read window, I can't go to previous/next message and the message isn't marked as read;
In write window, I can't send or save the message.
The only way to get out is to close and reopen the window. Thunderbird's main window keeps working OK, not having to be restarted. After reopening the window, it starts working again.

Reproducible: Always

Steps to Reproduce:
1.Open, reply, forward or create a message
2.Wait 'till TB starts compacting folders
3.Wait 'till TB finishes compacting folders
4.Try to do anything but close the window
(1 and 2 can be reversed)
Actual Results:  
Nothing

Expected Results:  
TB should obey whatever action required

Comment 1

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #0)

Local mail folder? (POP3, "Local Folders") Or IMAP folders? Both?

> (snip) while Thunderbird is compacting folders, (snip)

Which?
(a) Folder Context Menu/Compact, (b) File/Compact Folders, (c) By auto compact.

> In read window, I can't go to previous/next message and the message isn't marked as read;
> Steps to Reproduce:
>(snip)
> 4.Try to do anything but close the window

Compaction does do read operation only while compacting, except at end of compaction, delete old mail older file and rename nstmp to mail folder file name.
Compaction refreshes thread pane(nearly reset. scroll position etc. is lost) after end of compaction. It sounds thread pane related issue such as internal dead lock.)

> In write window, I can't send or save the message.
> The only way to get out is to close and reopen the window.
> Thunderbird's main window keeps working OK, not having to be restarted.
> After reopening the window, it starts working again.

Do you enable auto save?
If yes, it may be interfere between "auto save" and "end of compaction" each other. It may cause similar situation like zombie compose window(Bug 380275).

> Reproducible: Always

Really?
If yes, can you reproduce your problem always with -safe-mode of Thunderbird?

Comment 2

[WADA:World Anti-bad-Duping Agency]

Similar phenomenon to Bug 509042?

Comment 3

[Emerson Prado]

(In reply to comment #1)
> Local mail folder? (POP3, "Local Folders") Or IMAP folders? Both?
Local.

> Which?
> (a) Folder Context Menu/Compact, (b) File/Compact Folders, (c) By auto compact.
I've seen in (b) and (c). Tested with (a), messages disappeared - had to select another folder and get back to Inbox. Well, this is another issue.

> Do you enable auto save?
No. I disabled due to another problem.

> It may cause similar situation like zombie compose window(Bug 380275).
A bit similar, but the differences are that the window can be close and the message is not sent.

> > Reproducible: Always
> 
> Really?
> If yes, can you reproduce your problem always with -safe-mode of Thunderbird?
I can't tell. I opened a message, went back to the main TB window and hit File/Compact, but nothing appear to have happened. It usually says "Compacting folder X" and, in the end, "Folders compacted", but I saw none of these messages.

Comment 4

[Emerson Prado]

(In reply to comment #2)
> Similar phenomenon to Bug 509042?

In the sense that compacting folders seems the cause, yes. But the effect is totally diverse.

Comment 5

[Emerson Prado]

Oops, I duped myself - this bug is similar to bug 456746, reported by myself an year ago. I'll close this bug if none thinks it'll be better to close bug 456746 for the better description in this one.

Comment 7

[Wayne Mery (:wsmwk)]

Emerson, do you still see this problem when using version 3.1?

Comment 8

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this change was made in error, please respond to this bug with your reasons why.