Closed Bug 1153820 Opened 10 years ago Closed 9 years ago

crash in nsCOMPtr_base::assign_with_AddRef(nsISupports*) | nsMsgApplyFiltersToMessages::RunNextFilter()

Categories

(MailNews Core :: Filters, defect)

x86
All
defect
Not set
critical

Tracking

(firefox40 affected)

RESOLVED FIXED
Tracking Status
firefox40 --- affected

People

(Reporter: wsmwk, Unassigned)

References

Details

(Keywords: crash, regression, regressionwindow-wanted, Whiteboard: [regression:TB38?])

Crash Data

Crash does not exist prior to 38 beta This bug was filed from the Socorro interface and is report bp-e409e071-ad04-45b0-a99a-9892b2150403 (Kent's crash) ============================================================= 0 xul.dll nsCOMPtr_base::assign_with_AddRef(nsISupports*) xpcom/glue/nsCOMPtr.cpp 1 xul.dll nsMsgApplyFiltersToMessages::RunNextFilter() c:/builds/moz2_slave/tb-rel-c-beta-w32_bld-00000000/build/mailnews/base/search/src/nsMsgFilterService.cpp:1030 2 xul.dll nsMsgFilterAfterTheFact::AdvanceToNextFolder() c:/builds/moz2_slave/tb-rel-c-beta-w32_bld-00000000/build/mailnews/base/search/src/nsMsgFilterService.cpp:447 3 xul.dll nsMsgFilterService::ApplyFilters(int, nsIArray*, nsIMsgFolder*, nsIMsgWindow*, nsIMsgOperationListener*) c:/builds/moz2_slave/tb-rel-c-beta-w32_bld-00000000/build/mailnews/base/search/src/nsMsgFilterService.cpp:1109 Other examples: bp-ff9416ef-8dfd-42eb-b1a7-d11a12150407 bp-f245b35d-7dd6-4fa4-aba9-295a22150410
I'm guessing this is an issue of the underlying object being released and then called back from OnMessageClassified. Ownership management of the filter after the fact objects is tricky.
Crash Signature: [@ nsCOMPtr_base::assign_with_AddRef(nsISupports*) | nsMsgApplyFiltersToMessages::RunNextFilter()] → [@ nsCOMPtr_base::assign_with_AddRef(nsISupports*) | nsMsgApplyFiltersToMessages::RunNextFilter()] [@ nsCOMPtr_base::assign_with_AddRef | nsMsgApplyFiltersToMessages::RunNextFilter]
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
See Also: → 1186392
Depends on: 797710
You need to log in before you can comment on or make changes to this bug.