Closed Bug 691044 Opened 13 years ago Closed 10 years ago

Compaction empties tabs

Categories

(Thunderbird :: Toolbars and Tabs, defect)

7 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 520115

People

(Reporter: swsnyder, Unassigned)

Details

(Whiteboard: [dupeme])

Compaction removes the content in open tabs.  The tabs still exist and retain their titles, but the message content in the window is removed.

1. Start with several messages open in tabs.

2. Do File>>Compact on a folder that contains the tabbed message and can actually be compacted (has deleted messages to remove).

3. When the compaction operation is complete the tabs still exist, but each shows an empty window (no message content).

I've seen this with several messages in Inbox open.  When Compaction is run on the parent folder of Inbox ("Local Folders"?) the tabs are emptied of content.

Seen most recently with Thunderbird v7.0.1, but this behavior existed in prior versions too.
Not seeing that with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:9.0a2) Gecko/20111017 Thunderbird/9.0a2 on Imap folders.

Does it happen if the folder doesn't compact or does it need to be a folder where some files were previously deleted ?
(In reply to Ludovic Hirlimann [:Usul] from comment #1)
> Not seeing that with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:9.0a2)
> Gecko/20111017 Thunderbird/9.0a2 on Imap folders.

FWIW, this is on a POP3 account.
 
> Does it happen if the folder doesn't compact or does it need to be a folder
> where some files were previously deleted ?

This is in folders where messages have been deleted.  The problem happens on actual compression, not just on requesting that a Compact operation take place.
ref bug 520115
Whiteboard: [dupeme]
This occurs to me as well, using TB 17, but I remember it happening prior to TB 12.  

Specifically, if a message is open in a tab (or a separate window) from folder X, and then folder X is compacted, the tab/window is destroyed and message is closed.  Tabs (or windows) containing message from folders Y or Z are unaffected.  

I seen this behavior when compacting the Inbox, a subfolder of the Inbox, and the Sent folder as well.  

Simply choosing to compact is not sufficient to destroy the tab/window.  There must be expunged bytes to be compacted in order to trigger this behavior.

I do not see the error message re: "offset of mail is changed" stated in #520115, but I do get errors like the following, which if relevant suggest that an index or pointer is changing in the mail store, but the reference to the message in the open tab/window is not being updated:  

Timestamp: 10/22/2012 9:46:50 AM
Error: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgDBHdr.messageId]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://messenger/content/folderDisplay.js :: FolderDisplayWidget_saveSelection :: line 313"  data: no]
Source File: resource:///modules/errUtils.js
Line: 91

2012-10-22 09:46:50	gloda.index_msg	ERROR	Exception while attempting to mark message with gloda state afterdb commit [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgDBHdr.getUint32Property]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: resource:///modules/gloda/index_msg.js :: PendingCommitTracker_commitCallback :: line 159"  data: no]

2012-10-22 09:46:52	gloda.index_msg	WARN	Observed header that claims to be gloda indexed but that gloda has never heard of during compaction. In folder: mailbox://[[user]@[[domain]]/Inbox sketchy key: 202089812 subject: How about a poll?

Possibly related bugs:  

I do not see the behavior described here:  https://bugzilla.mozilla.org/show_bug.cgi?id=543708 (incoming mail destroys open message windows) 

I do see this behavior from time to time:  https://bugzilla.mozilla.org/show_bug.cgi?id=650267 (all open tabs display the same message).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.