This has happened a few times lately. Twice yesterday. When I hit to delete a message (come to think of it, the LAST message in a folder) by hitting the delete button in the header area, the title, from address, date, etc. becomes blank, BUT the area claimed by the original message still remains without disappearing. That is it looks as if there is a ghost message header with empty strings in subject, from, date, etc. This "empty" line only disappears, if I select another folder and refreshes the subject pane display and comes back to the original folder where the deletion occurs. Highly annoying. I think I have experienced this several times in a month or so. A screen dump is attached. TIA

This may be more serious than I thought. This is definitely a regression. TB 24.1.1 OK, I noticed something similar is happening under a different condition. But due to a point marked as *1 below, I think the root cause is the same, and so I am reporting this in this bugzilla. I noticed the problem in the following sequence. I tried to delete a message in the middle of a listing. They are shown in unread portion of the message list (in bold), but they were SPAMs and so I tried to delete them. Somehow when I clicked delete button, the particular message line is shown as read (in ordinary non-bold font) , but it is NOT deleted (!?) I deleted the message just above by hitting the DELETE button, but again the message line is shown in non-bold font but it is NOT deleted. Hmm... *1:Now I am posting this issue in this bugzilla entry BECAUSE I noticed that before the intended deletion of two messages above, I tried to delete a SPAM message AT THE END of the LISTING and quicky moved up the list to delete the two messages mentioned above., and I just realized that the LAST message line is shown as blank but with the symbols for marking still visible as in the original post! So, this time, I had more time luckily to investigate, and I looked in the debug web console. Then I found the tell-tale sign of errors there. I try to copy the relevant events one by one fro debug console. Sorry for the lengthy listing, but this seems important. (I wish there are ways to copy all the events in one operation, but it seems that copy and paste works only for one event at a time. Shall I file a bug on this?) Below are all the error events: starting from 12:00:32 (Below, date and others are shown in Japanese locale.) And this is under 32 bit Debian GNU/Linux. The original report is under Windows7, but I think the issue is very similar and root cause is the same (probably a bug or two in JavaScript code.) The timestamp looks like this and its meaning should be obvious. 時刻: 2013年11月28日 12時00分32秒 Date: 2013 11 28 12:00:32 (In English: 11 for months November.) (Japan standard time is ahead of Europe and America. So the date/time is for real.) 時刻: 2013年11月28日 12時00分32秒 エラー: this.folderDisplay.treeSelection is null ソースファイル: chrome://messenger/content/messageDisplay.js 行: 539 時刻: 2013年11月28日 12時04分19秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時04分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時04分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時04分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時07分17秒 エラー: this.folderDisplay.treeSelection is null ソースファイル: chrome://messenger/content/messageDisplay.js 行: 539 時刻: 2013年11月28日 12時09分19秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時09分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時09分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時09分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時14分19秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時14分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時14分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時14分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時15分05秒 エラー: this.folderDisplay.treeSelection is null ソースファイル: chrome://messenger/content/messageDisplay.js 行: 539 時刻: 2013年11月28日 12時17分57秒 エラー: this.folderDisplay.treeSelection is null ソースファイル: chrome://messenger/content/messageDisplay.js 行: 539 時刻: 2013年11月28日 12時19分06秒 エラー: this.folderDisplay.treeSelection is null ソースファイル: chrome://messenger/content/messageDisplay.js 行: 539 時刻: 2013年11月28日 12時19分19秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時19分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時19分19秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時19分59秒 エラー: An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80550018 [nsIMsgDBView.getMsgHdrAt]" nsresult: "0x80550018 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderDisplay.js :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://global/content/globalOverlay.js 行: 81 時刻: 2013年11月28日 12時19分59秒 エラー: Component returned failure code: 0x80550018 [nsIMsgDBView.getMsgHdrAt] ソースファイル: chrome://messenger/content/folderDisplay.js 行: 1898 時刻: 2013年11月28日 12時19分59秒 エラー: An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80550018 [nsIMsgDBView.getMsgHdrAt]" nsresult: "0x80550018 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderDisplay.js :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://global/content/globalOverlay.js 行: 81 時刻: 2013年11月28日 12時19分59秒 エラー: An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80550018 [nsIMsgDBView.getMsgHdrAt]" nsresult: "0x80550018 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderDisplay.js :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://global/content/globalOverlay.js 行: 81 時刻: 2013年11月28日 12時19分59秒 エラー: Component returned failure code: 0x80550018 [nsIMsgDBView.getMsgHdrAt] ソースファイル: chrome://messenger/content/folderDisplay.js 行: 1898 時刻: 2013年11月28日 12時19分59秒 エラー: An error occurred updating the cmd_delete command: [Exception... "Component returned failure code: 0x80550018 [nsIMsgDBView.getMsgHdrAt]" nsresult: "0x80550018 (<unknown>)" location: "JS frame :: chrome://messenger/content/folderDisplay.js :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://global/content/globalOverlay.js 行: 81 時刻: 2013年11月28日 12時24分20秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時24分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時24分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時24分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時29分20秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時29分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時29分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時29分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 I hope this helps.

= as an additional testing, at this point where previoulsy I tried to delete two messages, and thus is shown as read, but not still deleted, and the last message was presumably deleted, but a fantom line with symbol marks still visible there, I hit DELETE button again on one of the two was-deleted-but-failed messages. Several additional events are shown in debug console. I recorded them as below. I think the first two events were shown while I was moving in the message list (from the timestamp shown, but I am not entirely sure. I was typing this text in an editor window while these events showed up, I think.) 時刻: 2013年11月28日 12時34分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時34分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時39分20秒 <--- this is when I hit the DELETE again エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時39分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時39分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時39分20秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 ==== Now let me find out what happens when I switch the displayed folder to a different one, and come back to the original (that is, Inbox) Before the switch: At the end of the list: an empty message line (but visible symbol marks) a few lines above (counted from the strange line: 3rd, 4th), a couple of two messages that I tried to delete, but still there. My expectation based on the buggy behavior in the original post: the last empty message line would disapper, but the two messages that could not be deleted will still be shown. Actual result: Yes, the last fantom line is gone. Meaning that it was deleted (but the display was not correctly updated). The two lines that could not be deleted are still there. I wish I had captured the screen before doing this. Somehow one of the two lines, the upper one, for which deletion failed is still shown in BOLD letter (that is unread). Something is really screwed up. Display update failure. Deletion failure (possibly due to the incorrect ID information passed to delete routine due to the screwed up display?) This is definitely a regression.

Things are getting more interesting, but I am afraid that unless I restart TB, there may be harm to the database, so this is the last bugzilla entry about the events recorded in the debug console. But TB is continously logging errors like this. I was typing the bugzilla message, etc. and so did not much do any invasive operation on my own. 時刻: 2013年11月28日 12時54分21秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時54分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時54分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時54分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時59分21秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 12時59分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時59分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 12時59分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 13時01分27秒 エラー: this.folderDisplay.treeSelection is null ソースファイル: chrome://messenger/content/messageDisplay.js 行: 539 I think once the internal database is screwed up, any periodical update operation would fail like this until TB is restarted :-( As I type this text in another editor window, I noticed additiおnal events are logged automatically. 時刻: 2013年11月28日 13時04分21秒 エラー: [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 :: FolderDisplayWidget.prototype.selectedMessage :: line 1898" data: no] ソースファイル: chrome://messenger/content/tabmail.xml 行: 905 時刻: 2013年11月28日 13時04分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 13時04分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 13時04分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 13時04分21秒 エラー: msgHdr is null ソースファイル: chrome://messenger/content/mailTabs.js 行: 334 時刻: 2013年11月28日 13時05分17秒 エラー: formatURL: Couldn't find value for key: TIME_SESSION_RESTORED ソースファイル: resource://gre/components/nsURLFormatter.js 行: 117 (Flurry of "LOG" events related to addon update are shown following the above formatURL error, and then ends with the following 時刻: 2013年11月28日 13時05分19秒 警告: WARN addons.updates: Update manifest for {972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property ソースファイル: resource://gre/modules/AddonUpdateChecker.jsm 行: 312 The group of events are repeated at every five minutes. Some of them have the "this.folderDisplay.treeSelction is null" at the end. It continued past 13:39. TIA

The problem came back again. TB 24.2.0 under Debian GNU/Linux 32-bit. In the attachment, there are four empty lines at the end: something is wrong with the display. I tried to delete the "[SPAM]" messages when TB became unresponsive and once it began accepting mouse input, etc., the display became strange. I looked in the error console and found the following at the end: 時刻: 2014年02月10日 10時31分46秒 エラー: this._sort[aIndex] is undefined ソースファイル: resource://gre/modules/dbViewWrapper.js 行: 1509 Whether the above is the result or the cause of the issue is not unclear. Before the above error message, I see some syntax errors that include lines like the following: 時刻: 2014年02月10日 10時21分44秒 警告: 色であるべきところが 'collapse' になっています。 'border' の値をパース中にエラーが発生しました。 このスタイル宣言は無視されました。 (My translation: Where color should be specified 'collapse' was specified instead. An error occured during the parsing of the value of the 'border'. This style declaration is ignored. (I am not sure where the following source code came from. Maybe an HTML in the spam message?) ソースファイル: about:blank 行: 79, 列: 3112 ソースコード: *[class].hero_bg {background-repeat: no-repeat;background-position: top right;}*[class].bg_anniversary,*[class].bg_position {background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/email/campaigns/network_updates_digest/herobg_ribbon_162x172_v01.png);}*[class].bg_endorsement.digest,*[class].bg_skill {background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/email/campaigns/network_updates_digest/herobg_skills_135x193_v01.png);}*[class].bg_post {background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/email/campaigns/network_updates_digest/herobg_comment_160x141_v01.png);}*[class].bg_connection {background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/email/campaigns/network_updates_digest/herobg_connections_193x163_v01.png);}*[class].bg_otherprofileupdates {background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/email/campaigns/network_updates_digest/herobg_profile_184x129_v01.png);background-position: bottom right;}*[class].bg_pictureshare {background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/email/campaigns/network_updates_digest/herobg_photo_158x129_v01.png);background-position: bottom right;}*[class].hero_bg_ovr_none {background-image: none;}html { -webkit-text-size-adjust: none; }body { background-color: #DFDFDF; padding: 0; margin: 0; width: 100%; margin: 0 auto; }@media all and (max-width: 590px){*[class].responsive{width:290px !important;}*[id]#center {width:50%; margin: 0 auto; display:table;}*[class].responsive-spacer table{width: 20px !important; }*[class].vspacer{ margin-top: 10px !important; margin-bottom: 15px !important; margin-left: 0 !important; }*[class].res-font14{font-size:14px !important;}*[class].res-font16{font-size:16px !important;}*[class].res-font13{font-size:13px !important;}*[class].res-font12{font-size:12px !important;}*[class].res-font10{font-size:10px !important;}*[class].res-font18{font-size:18px !important;}*[class].res-font18 span{font-size: 18px !important;}*[class].responsive-50per{ width: 100% !important;}*[class].responsive-spacer70{ width: 70px !important; }*[class].hideIMG{ height: 0px !important; width: 0px !important; }*[class].res-height30{ height: 30px !important; }*[class].res-height20{ height: 20px !important; }*[class].res-height20 div{ height: 20px !important; }*[class].res-height10{ height: 10px !important; }*[class].res-height10 div{ height: 10px !important; }*[class].res-height10.email-spacer div { height: 10px !important; min-height: 10px !important; line-height: 10px !important; font-size: 10px !important; }*[class].res-height0 { height: 0px !important; }*[class].res-height0 div{ height: 0px !important; }*[class].res-width280{ width: 280px !important; }*[class].res-width25{ width: 25px !important; }*[class].res-width10{ width: 10px !important; }*[class].res-width10 table{ width: 10px !important; }*[class].res-width120 { width: 120px !important; }*[class].res-padding{ width: 0 !important; }*[class].res-padding table{ width: 0 !important; }*[class].cellpadding-none{ width: 0px !important; }*[class].cellpadding-none table{ border: collapse !important; }*[class].cellpadding-none table td{ padding: 0 !important; }*[class].display-none{ display: none !important; }*[class].display-block{ display: block !important; }*[class].remove-margin{ margin: 0 !important; }*[class].remove-border{ border: none !important; }*[class].res-img60{ width: 60px !important; height: 60px !important; }*[class].res-img75{ width: 75px !important; height: 75px !important; }*[class].res-img100{ width: 100px !important; height: 100px !important; }*[class].res-img320{ width: 320px !important; height: auto !important; position: relative;}*[class].res-img90x63{ width: 90px !important; height: 63px !important;}*[class].res-border{border-top: 1px solid #E1E1E1 !important;}*[class].responsive2col{width: 100% !important;}*[class].center-content{text-align: center !important;}*[class].hide-for-mobile{ display: none !important; }*[class].show-for-mobile{ width: 100% !important; max-height: none !important; visibility: visible !important; overflow: visible !important; float: none !important; height: auto !important; display: block !important; }*[class].responsive-table { display: table !important; }*[class].responsive-row { display: table-row !important; }*[class].responsive-cell { display: table-cell !important; }*[class].fix-table-content{ table-layout: fixed; }*[class].res-padding08{ padding-top:8px; }*[class].hero_bg {background-image: none !important;}*[class].show_hero {max-height: none !important;visibility: visible !important;overflow: visible !important;float: none !important;display: table-cell !important;width: 270px !important;}*[class].cta_text {max-height: none !important;visibility: visible !important;overflow: visible !important;float: none !important;display: table-cell !important;width: 100% !important;color:#0077b5 !important;font-size:12px !important;}*[class].left_10 {padding-left:10px;}*[class].limit_4_items:nth-child(n+8) {display: none !important;}}@media all and (-webkit-min-device-pixel-ratio : 1.5) {*[id]#base-header-logo {background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/email/logos/logo_linkedin_tm_email_197x48_v1.png) !important;background-size: 95px;background-repeat: no-repeat;width: 95px !important;height: 21px !important;}*[id]#base-header-logo img {display: none;}*[id]#base-header-logo a {height: 21px !important;}*[id]#base-header-logo-china {background-image: url(http://s.c.lnkd.licdn.com/scds/common/u/images/email/logos/logo_linkedin_tm_china_email_266x42_v1.png) !important;background-size: 133px;background-repeat: no-repeat;width: 133px !important;height: 21px !important;}*[id]#base-header-logo-china img {display: none;}*[id]#base-header-logo-china a {height: 21px !important;}} Hmm, the above source code includes a reference to s.c.lnkd.licdn.com, and so may be related to the first header line shown in the message list window. Further before the above error, I see an error like this. 時刻: 2014年02月10日 10時21分41秒 警告: 宣言ブロックを開始する '{' であるべきところが 'Section1' になっています。 (My translation: WARNING: A "{" to start a declaration was expected, but 'Section1' was found. ソースファイル: about:blank (Source File: about:blank) 行: 711, 列: 6 ソースコード: @page Section1 It is a little difficult to figure out why a blank page contains something that is not parsed correctly. The above error is followed by the following error. 時刻: 2014年02月10日 10時21分41秒 警告: @ ルール '@list' を識別できないか、パースエラーが発生しました (WARNING: @rule '@list' cannot be recognized OR a parse error occurred.) ソースファイル: about:blank 行: 717, 列: 1 ソースコード: @list l0 It is possibly a memory corruption or something. I now notice from "About TB" display when I check the version of TB, that a restarting TB is required to update the executable and so will do so, hoping this problem will be solved. TIA

One more clue. I notice that when the display got corrupted, I think TB was downloading e-mails. I think the four strange lines correspond to four new e-mails that just arrived (becuase I was trying to delete the LAST spam message and that e-mail was positioned ABOVE these phantom lines.) If so, I think TB now had/has a regression concerning proper locking of internal database for header display or something. TIA

After the restart prompted by the "About TB" help menu, TB showed the Inbox correctly. The four strange blank lines seemed to correspond to FOUR (4) spam-emails that are moved to Junk folder. I checked the received header line to see when it was received my local mail server, etc. They came in when TB started to behave erratically. (Not sure if they were automatically moved there, or were moved there my manual deletion [when the display was not quite correctly updated.]) I hope the above may give a clue to where to look... TIA

Have you seen this in a more current version?

I was seeing this June, July time frame even. It *seemed* that when the system is loaded and thus the internal message database update is slow, and I tried to hit the delete button again maybe before the internal message database is not finished in order to delete another message, this seemed to happen more often. *BUT*, lately, I noticed the following problem which is solved by a new patch. I am beginning to think the major root cause could have been this bug. Bug 1066459 - When the tree scrolled to the last page and last row, It's showed a blank row There was a redraw failure when a list is shrunk by deleting an element there. This sounds suspiciously similar to the problem I originally reported (!) Please notice the comment put in one interim (?) version of the patch: https://bug1085050.bugzilla.mozilla.org/attachment.cgi?id=8507506 // Note that we may be "over scrolled" at this point; that is the + // current mTopRowIndex may be larger than mRowCount - mPageLength. + // This can happen when items are removed for example. (bug 1085050) <===*** Actually, I filed bug 1085050 myself when I notice the locally built DEBUG BUILD version of C-C TB crashed when I deleted a message by hitting delete from context-menu. The crash was caused by MOZ_ASSERT() placed by the previous patch. I suspect that, instead of crashing due to MOZ_ASSERT(), the previous version of released TB failed to redraw the message list correctly. Hope the next release based on the current trunk will not have this problem.

Still see this?

(In reply to Wayne Mery (:wsmwk) from comment #10) > Still see this? Wayne, sorry I could not respond. I was in the middle of updating my patch sets to deal with I/O error issues and unbuffered write of mail and attachments when I noticed that the patch seems to be no longer correct after I updated the source tree about 10 days ago. (Before with ealry summer source tree, the patch passed |make mozmill| and xpcshell-tests with flying colors. No longer. So I was in the middle of serious file comparison, etc. when the PC I work on became rather unreliable. It cannot stay put overnight any more. I get a blank screen when I look at the display after running a test overnight :-( I have found a temporary replacement PC for preserving the current hardware setup (internal disks and external disks connected via eSATA cable), but it will arrive on Sunday. In the meantime, I plan to move over to a brand new 8 core/ 16 thread machine using AMD Ryzen, but the PC case for that has not arrived yet. CPU, motherboard, memory, etc. are already in my hands. I am waiting for the deliery right now in the evening. Then at least I can possibly begin moving some files files to the new machine. I would prefer to compile and link and test for linux binary at least locally. I need to rely on mozilla compilation infrastructure for testing Mac OS X version and Windows version, though. Please wait for another 7 days or something before dust settles down. Hardware malfunction hits when we least suspect it :-(