Closed Bug 1859470 Opened 2 years ago Closed 1 year ago

Crash in [@ nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf ] via nsMsgXFViewThread::RemoveChildHdr

Categories

(Thunderbird :: General, defect)

Unspecified
Windows 10
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 646168

People

(Reporter: wsmwk, Unassigned)

Details

(Keywords: crash)

Crash Data

A variation of Bug 646168 - crash (shift-del) deleting/moving mail in normal or Unified Folders view ?

Crash report: https://crash-stats.mozilla.org/report/index/09369134-f9da-4e80-b224-5abb80231017

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0  xul.dll  nsTArray_base<nsTArrayInfallibleAllocator, nsTArray_RelocateUsingMemutils>::Length const  xpcom/ds/nsTArray.h:410
0  xul.dll  nsTArray_Impl<nsRefreshDriver::ObserverData, nsTArrayInfallibleAllocator>::IndexOf const  xpcom/ds/nsTArray.h:1343
0  xul.dll  nsTArray_Impl<nsRefreshDriver::ObserverData, nsTArrayInfallibleAllocator>::IndexOf const  xpcom/ds/nsTArray.h:1361
0  xul.dll  nsAutoTObserverArray<nsRefreshDriver::ObserverData, 0>::IndexOf const  xpcom/ds/nsTObserverArray.h:150
0  xul.dll  nsRefreshDriver::RemoveRefreshObserver  layout/base/nsRefreshDriver.cpp:1432
1  xul.dll  nsRefreshDriver::WillRefresh  layout/base/nsRefreshDriver.cpp:3051
2  xul.dll  nsMsgXFViewThread::RemoveChildHdr  mailnews/base/src/nsMsgXFViewThread.cpp:291
3  xul.dll  nsMsgSearchDBView::OnHdrDeleted  mailnews/base/src/nsMsgSearchDBView.cpp:223
4  xul.dll  nsMsgDatabase::NotifyHdrDeletedAll  mailnews/db/msgdb/src/nsMsgDatabase.cpp:756
5  xul.dll  nsMsgDatabase::DeleteHeader  mailnews/db/msgdb/src/nsMsgDatabase.cpp:1785
Flags: needinfo?(mkmelin+mozilla)

No idea, sorry.

Flags: needinfo?(mkmelin+mozilla)

Bp-576af534-8d3c-4f67-901e-3e91f0231025 from a few days ago states "occurred during sleep phase of computer"

See Also: → 646168

However, the signature pretty much ends starting with 115.6.0. But I don't see what would have fixed this, nor what signature would have increased:

  • 115.6.0 landed https://mzl.la/3Sm5czS
  • Bug 646168 isn't yet fixed in esr - crash (shift-del) deleting/moving mail in normal or Unified Folders view? [@ nsMsgXFViewThread::RemoveChildHdr] via nsMsgSearchDBView::OnHdrDelete - m_view is already destroyed or invalid

Nevermind, I already documented this in bug 646168 comment 98

Crash Signature: [@ nsTArray_base<T>::Length | nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf] → [@ nsTArray_base<T>::Length | nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf] [@ nsRefreshDriver::GetVsyncId]
Summary: Crash in [@ nsTArray_base<T>::Length | nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf] → Crash in [@ nsTArray_base<T>::Length | nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf] via nsMsgXFViewThread::RemoveChildHdr
See Also: → 1878469
Crash Signature: [@ nsTArray_base<T>::Length | nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf] [@ nsRefreshDriver::GetVsyncId] → [@ nsTArray_base<T>::Length | nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf] [@ nsRefreshDriver::GetVsyncId] [@ nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf ]
Summary: Crash in [@ nsTArray_base<T>::Length | nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf] via nsMsgXFViewThread::RemoveChildHdr → Crash in [@ nsTArray_Impl<T>::IndexOf | nsTArray_Impl<T>::IndexOf | nsAutoTObserverArray<T>::IndexOf ] via nsMsgXFViewThread::RemoveChildHdr

This apparently doesn't happen anymore in 115.9 and seems to be just duplicate of Bug 646168 (crash originating in nsMsgXFViewThread::RemoveChildHdr) .

Status: NEW → RESOLVED
Closed: 1 year ago
Duplicate of bug: 646168
Resolution: --- → DUPLICATE
See Also: 646168
See Also: 1878469
You need to log in before you can comment on or make changes to this bug.