Closed Bug 478822 Opened 16 years ago Closed 9 years ago

crash quicksearch subject in threaded view (single folder) [@ nsMsgDBView::GetInsertIndexHelper]

Categories

(Thunderbird :: Search, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wsmwk, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [rare])

Crash Data

build 20090213031214 crash quicksearch subject in threaded view (single folder) [@ nsMsgDBView::GetInsertIndexHelper] 1. subject threaded in single folder (not search) 2. have moved some messages from the folder by drag and drop to other folders, and delete 3. initiated quick search of subject crash no hits on crash-stats except mine, perhaps only I get these crashes :( unable to thoroughly research via crash-stats - too many timeouts not researching this now, but perhaps the same as Bug 420257 virtual folder crash after change search criteria [@ @0x746e6574 - @ nsMsgSearchOfflineMail::OpenSummaryFile()] Bug 465940 - crash [@ nsMsgDBView::SecondarySort(unsigned int, nsISupports*, unsigned int, nsISupports*, viewSortInfo*)] bp-e36c6901-0ec4-46e0-9ffa-90aeb2090216 nsMsgDBView::GetInsertIndexHelper nsMsgDBView.cpp:4637 nsMsgQuickSearchDBView::SortThreads nsMsgQuickSearchDBView.cpp:489 nsMsgThreadedDBView::Sort nsMsgThreadedDBView.cpp:360 nsMsgThreadedDBView::InitSort nsMsgThreadedDBView.cpp:581 nsMsgThreadedDBView::InitThreadedView nsMsgThreadedDBView.cpp:161 nsMsgQuickSearchDBView::Open nsMsgQuickSearchDBView.cpp:74 NS_InvokeByIndex_P xpcom/reflect/xptcall/src/md/win32/xptcinvoke.cpp:101 js_GetProperty js/src/jsobj.cpp:3904 XPCWrappedNative::CallMethod js/src/xpconnect/src/xpcwrappednative.cpp:2424 XPC_WN_CallMethod js/src/xpconnect/src/xpcwrappednativejsops.cpp:1479 kreeger says he no longer sees this but I'll cite it anyway, Bug 401429 - Sorting message folder lists crashes on 10.5
Depends on: 283238
Component: Mail Window Front End → Search
QA Contact: front-end → search
Depends on: 641137
Crash Signature: [@ nsMsgDBView::GetInsertIndexHelper]
only a half dozen crashes in a month for current versions. and at least two stacks for nsMsgDBView::GetInsertIndexHelper(nsIMsgDBHdr*, nsTArray<unsigned int, nsTArrayDefaultAllocator>&, nsCOMArray<nsIMsgFolder>*, int, int) ... bp-925d86f2-88a2-40f6-844c-861e42130104 0 xul.dll nsMsgDBView::GetInsertIndexHelper mailnews/base/src/nsMsgDBView.cpp:5251 1 xul.dll nsMsgDBView::GetInsertIndex mailnews/base/src/nsMsgDBView.cpp:5301 2 xul.dll nsMsgGroupView::AddHdrToThread mailnews/base/src/nsMsgGroupView.cpp:301 3 xul.dll nsMsgGroupView::OnNewHeader mailnews/base/src/nsMsgGroupView.cpp:522 4 xul.dll nsMsgXFVirtualFolderDBView::OnSearchHit mailnews/base/src/nsMsgXFVirtualFolderDBView.cpp:279 bp-7f555586-5b7e-4b4e-8ae5-0247e2130101 0 xul.dll nsMsgDBView::GetInsertIndexHelper mailnews/base/src/nsMsgDBView.cpp:5224 1 xul.dll nsMsgDBView::GetInsertIndex mailnews/base/src/nsMsgDBView.cpp:5301 2 xul.dll nsMsgDBView::AddHdr mailnews/base/src/nsMsgDBView.cpp:5341 3 xul.dll nsMsgThreadedDBView::OnNewHeader mailnews/base/src/nsMsgThreadedDBView.cpp:581 4 xul.dll nsMsgDBView::OnHdrAdded mailnews/base/src/nsMsgDBView.cpp:5956 5 xul.dll nsMsgDatabase::NotifyHdrAddedAll mailnews/db/msgdb/src/nsMsgDatabase.cpp:870 6 xul.dll nsMsgDatabase::AddNewHdrToDB mailnews/db/msgdb/src/nsMsgDatabase.cpp:3437 7 xul.dll nsParseNewMailState::PublishMsgHeader mailnews/local/src/nsParseMailbox.cpp:1875 8 xul.dll nsPop3Sink::IncorporateComplete mailnews/local/src/nsPop3Sink.cpp:873
Crash Signature: [@ nsMsgDBView::GetInsertIndexHelper] → [@ nsMsgDBView::GetInsertIndexHelper] [@ nsMsgDBView::GetInsertIndexHelper(nsIMsgDBHdr*, nsTArray<unsigned int, nsTArrayDefaultAllocator>&, nsCOMArray<nsIMsgFolder>*, int, int) ]
Whiteboard: [rare]
Christos writes "not seen this in a long time"
Hm, so at http://hg.mozilla.org/releases/comm-release/annotate/1f02ae595203/mailnews/base/src/nsMsgDBView.cpp#l5215 we have EntryInfo1.folder->Release(); and then it crashes when EntryInfo1.folder is used a few lines down. Why isn't it always crashing?
You need to log in before you can comment on or make changes to this bug.