crash [@ nsMsgDBView::GetIndexForThread] attempting delete in saved search, cross folder search Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090118 Shredder/3.0b2pre deleted last message (of 3), in last thread in a cross folder saved search. on restart, if my memory is correct, all 3 messages were still in the original, real folder. For this top of stack, mine is the one on crash-stats going back 2 weeks. And no open bugs, nor bugs with activity in the last 12 months, cite the top 3 frames except Bug 75296 - closed long ago bp-9501d794-7c29-4e9c-a452-c6a0c2090118 nsMsgDBView::GetIndexForThread nsMsgDBView.cpp:4492 nsMsgSearchDBView::MoveThreadAt nsMsgSearchDBView.cpp:563 nsMsgSearchDBView::AddHdrFromFolder nsMsgSearchDBView.cpp:494 nsMsgXFVirtualFolderDBView::OnSearchHit nsMsgXFVirtualFolderDBView.cpp:316 nsMsgXFVirtualFolderDBView::OnNewHeader nsMsgXFVirtualFolderDBView.cpp:150 nsMsgDBView::OnHdrAdded nsMsgDBView.cpp:5318 nsMsgDatabase::NotifyHdrAddedAll nsMsgDatabase.cpp:683 nsMsgDatabase::AddNewHdrToDB nsMsgDatabase.cpp:3043 nsImapMailDatabase::AddNewHdrToDB nsImapMailDatabase.cpp:156 nsImapMailFolder::NormalEndHeaderParseStream nsImapMailFolder.cpp:2925 nsImapMailFolder::ParseMsgHdrs nsImapMailFolder.cpp:2760 NS_InvokeByIndex_P xpcom/reflect/xptcall/src/md/win32/xptcinvoke.cpp:101 nsEventQueue::GetEvent xpcom/threads/nsEventQueue.cpp:100 nsProxyObjectCallInfo::Run xpcom/proxy/src/nsProxyEvent.cpp:181 nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:510 NS_ProcessNextEvent_P nsThreadUtils.cpp:227

crashed again bp-b268992e-9afd-4326-bd34-2f3032090118 - not sure if I was in saved search at that point, or in real folder. Includes same stack as above, bug instead of nsMsgDBView::GetIndexForThread as top of stack, the top 3 frames are msvcr80.dll@0x1537a nsTArray_base::ShiftData nsTArray.cpp:173 nsTArray<nsIFrame*>::ReplaceElementsAt<nsIFrame*> nsTArray.h:494 so this crash may be bug 460036, and this bug/comment 0 may be a variation of 460036.

closing WFM. never seen this again. and nothing found in crash-stats. I'd put fuller top of stack in summary, but crash-stats cant pull up my crashes