Closed Bug 916450 Opened 12 years ago Closed 9 years ago

crash in nsMsgDBFolder::NotifyFolderEvent(nsIAtom*) moving/deleting messages

Categories

(MailNews Core :: Database, defect)

Product:
MailNews Core
Component:
Database
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: wsmwk, Unassigned)

Details

(Keywords: crash)

Crash Data

crash in nsMsgDBFolder::NotifyFolderEvent(nsIAtom*) moving/deleting messages This bug was filed from the Socorro interface and is report bp-d1db2d68-254c-4ee2-b4a5-5bdc92130812. ============================================================= 0 xul.dll nsMsgDBFolder::NotifyFolderEvent(nsIAtom *) mailnews/base/util/nsMsgDBFolder.cpp 1 xul.dll nsMsgDBFolder::UpdateTimestamps(bool) mailnews/base/util/nsMsgDBFolder.cpp 2 xul.dll nsMsgLocalMailFolder::CopyMessages(nsIMsgFolder *,nsIArray *,bool,nsIMsgWindow *,nsIMsgCopyServiceListener *,bool,bool) mailnews/local/src/nsLocalMailFolder.cpp 3 xul.dll nsMsgCopyService::DoNextCopy() mailnews/base/src/nsMsgCopyService.cpp 4 xul.dll nsMsgCopyService::DoCopy(nsCopyRequest *) mailnews/base/src/nsMsgCopyService.cpp 5 xul.dll nsMsgCopyService::CopyMessages(nsIMsgFolder *,nsIArray *,nsIMsgFolder *,bool,nsIMsgCopyServiceListener *,nsIMsgWindow *,bool) mailnews/base/src/nsMsgCopyService.cpp @0x0 | nsMsgDBFolder::NotifyFolderEvent bp-c472d64b-a3c4-4d65-9f20-0cc822130801 nsMsgDBFolder::NotifyFolderEvent bp-ad140c0a-9dbf-4ead-ba71-bd7bb2130911 Most crashes are via nsMsgDBFolder::UpdateTimestamps A couple examles that are not: bp-5a422901-9d50-4485-9091-56d272130909 nsMsgDBFolder::OnJunkScoreChanged(nsIDBChangeListener *) bp-84109ddf-1f7f-4e91-85bf-351fc2130816 nsMailDatabase::GetSummaryValid
Component: Backend → Database
3/4 of the stacks are odd. And what's left almost no crashes per week. So I doubt there's anything anything actionable here.
Whiteboard: [closeme 2017-01-01]
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2017-01-01]
You need to log in before you can comment on or make changes to this bug.