Rodrigo Perez Reporter
	Description • 13 years ago

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; pt-BR; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9

When you open a few e-mail messages and try to navegate from one tab to another it will only show the last message openeded. There is one other problem but i still can't reproduce how it happenes, basiclly the program stop showing the messages when a click over on message. I'll try do find and will post here.

Reproducible: Always

Steps to Reproduce:
1.Open thunderbird
2.Open a message (1)
3.Come back to the tab where your accounts are
4.Open anoher message (2)
5. Now you have 3 tabs open (mail account) (1) (2), if you click on the tab (1) it will show message (2).


Expected Results:  
show the message opened.

	Ludovic Hirlimann [:Usul]
	Comment 1 • 13 years ago

Do you have the issue when you start Thunderbird in -safe-mode ? (see http://support.mozillamessaging.com/en-US/kb/Safe+Mode) 


Any Errors in Tools -> Error console ?

	O.Gopal
	Comment 2 • 13 years ago

I intermittently encounter the same bug -- changing tabs fails to change messages -- with Thunderbird under Ubuntu.

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11.

	mgoldey
	Comment 4 • 12 years ago

I have experienced this bug as well, on and off, for about six months.  At present, I have three tabs open -- the Inbox, and two messages from that Inbox.  Both messages tabs display the contents of the most recent e-mail in the Inbox. 

A little experimenting shows that the two message tabs show whichever message is highlighted in the main (leftmost) tab, the one that shows all of my accounts and mail folders.  If I click on a message in the Inbox, or any subfolder, that message is then displayed in the other two message tabs. This is true even if I select a message in a different account entirely. 

There are two messages repeated in the Error Console.  One, which appears all the time and is probably irrelevant, is:

Timestamp: 11/16/2012 2:03:57 PM
Warning: XUL box for _moz_generated_content_before element contained an inline #text child, forcing all its children to be wrapped in a block.
Source File: chrome://messenger/content/folderDisplay.js
Line: 1611

The other one, which is likely related to this bug, is:

Timestamp: 11/16/2012 2:03:55 PM
Error: An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgDBView.getMsgHdrAt]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://messenger/content/folderDisplay.js :: <TOP_LEVEL> :: line 1900"  data: no]
Source File: chrome://global/content/globalOverlay.js
Line: 81

There are about 100 of these, generated within the few minutes before I noticed the error, and once I started playing around with it.  Another 100 or so of the same error messages were generated at about the time I restarted the browser.  At the time of restart, the two message tabs were already open, and were automatically re-opened when TB restarted (except, of course, the message content is wrong).

One last thing -- I compacted my inbox at around the same time I noticed the problem.  Can't say for sure that the compaction pre-dates the error and error messages, but it probably does.  Betcha a donut that the message index for the messages in the open tabs has changed, TB can't find the right message, so it's displaying the "active" message by default.

TB 16.02, but this happens in TB 17, too (I used to get the beta updates).

	mgoldey
	Comment 5 • 12 years ago

Now using TB 17, and bug has two slight twists:  

1) After compaction, all open tabs contain the same message, which happens to be one of the messages open in one of the tabs.  In other words, one of the message tabs holds the correct message.  That message is buried in a subfolder and has not been highlighted in the inbox tab for days and days.  

2) But there's a further twist:  if I go back to the inbox tab, there is a highlighted message, of course.  Then, if I start clicking on the open message tabs, most of the open tabs will display the contents of the highlighted message.  When I get to the message tab that correctly displays its message, that tab continues to show the correct message, and then all other open messages display that same message, even if they previously showed the message that is highlighted on the inbox tab.

As before, the error console is full of errors like these:  

Timestamp: 11/27/2012 8:51:02 PM
Error: NS_ERROR_INVALID_POINTER: Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgDBView.getMsgHdrAt]
Source File: chrome://messenger/content/messageDisplay.js
Line: 426

Timestamp: 11/27/2012 8:51:02 PM
Error: An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [nsIMsgDBView.getMsgHdrAt]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://messenger/content/folderDisplay.js :: <TOP_LEVEL> :: line 1910"  data: no]
Source File: chrome://global/content/globalOverlay.js
Line: 81

Also, this bug may be related:  https://bugzilla.mozilla.org/show_bug.cgi?id=691044   Many times, upon compacting, the open message tabs are simply closed.  That happened a few days ago.  It didn't happen this last time, though, and instead I got big by this bug.

	Wayne Mery (:wsmwk)
	Comment 6 • 12 years ago

this might not be correct component, but hopefully better than General

	Wayne Mery (:wsmwk)
	Comment 7 • 9 years ago

rodrigo, O.Gopal

Do you still see this problem when  using version 38?


(In reply to mgoldey from comment #5)
>...
> Also, this bug may be related: 
> https://bugzilla.mozilla.org/show_bug.cgi?id=691044   Many times, upon
> compacting, the open message tabs are simply closed. 

That would now bug 520115

	O.Gopal
	Comment 8 • 9 years ago

(In reply to Wayne Mery (:wsmwk, use Needinfo for questions) from comment #7)
> rodrigo, O.Gopal
> 
> Do you still see this problem when  using version 38?
> 
> 
> (In reply to mgoldey from comment #5)
> >...
> > Also, this bug may be related: 
> > https://bugzilla.mozilla.org/show_bug.cgi?id=691044   Many times, upon
> > compacting, the open message tabs are simply closed. 
> 
> That would now bug 520115

Am using 40.0.3 and haven't seen that problem in a long time.

	mgoldey
	Comment 9 • 9 years ago

I am using 40.0 and I just did a compaction of my inbox, with four open message tabs.  All of those message tabs closed themselves after the compaction completed.

The error console contains about 100 messages like these:

2015-09-10 09:57:03	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.tld/Inbox sketchy key: 1042354902 subject: Condolences - Ward

(user@domain.tld is a substitution, of course)

Normally, whenever I compact, I experience the behavior described in the first post:  each open tab displays the same content, typically the content of one of the tabs prior to compacting.  All of the open tabs are borked and unusable.

In the past year or so, I have occasionally noticed that one of the tabs will still contain the correct message and remain a viable, uncorrupted message tab.  Since I compact regularly, my hypothesis is that the compaction and any re-ordering of keys, etc., occurs within the most recent messages, leaving the structure of older messages alone.  Therefore, a sufficiently-old message in an open tab will keep its message key (or whatever the mechanism is) because there is nothing older than it or "above" it to compact.  Such a message in an open tab will remain usable after compaction.  But anything newer or "below" the location of the oldest deleted message -- the message whose former space is being compacted -- will be corrupted.


I have not seen auto-closing tabs lately. They may have closed automatically I opened and then closed the Help > About window right after compacting stopped.  I have a feeling that the "clean up unwanted windows" routine also picks up defunct message tabs.  Just a guess.

	Phoenix
	Comment 10 • 9 years ago

Resolved per whiteboard and Comment 8
mgoldey, your issue differs from reported in this bug, please fill new one