Crash in Abort | mozalloc_abort | NS_DebugBreak | nsDebugImpl::Abort | NS_InvokeByIndex

RESOLVED INCOMPLETE

Status

()

Core
General
--
critical
RESOLVED INCOMPLETE
2 years ago
2 years ago

People

(Reporter: marcia, Unassigned)

Tracking

({crash})

48 Branch
x86
Windows 7
crash
Points:
---

Firefox Tracking Flags

(firefox47 wontfix, firefox48+ wontfix, firefox49+ fix-optional, firefox50+ fix-optional)

Details

(crash signature)

[Tracking Requested - why for this release]: New signature that we should potentially investigate before 48 ships

This bug was filed from the Socorro interface and is 
report bp-58d2a422-3734-41b0-9154-1c6172160623.
=============================================================

Bucketing this in Core | General for now since I don't know exactly where to place it. Link to crashes:
https://crash-stats.mozilla.com/report/list?signature=Abort%20%7C%20mozalloc_abort%20%7C%20NS_DebugBreak%20%7C%20nsDebugImpl%3A%3AAbort%20%7C%20NS_InvokeByIndex#tab-reports

I noticed this in the explosive report for 48, but the crashes occur in 47 and 49 as well. Comments mention memory issues and crashing on restart or exit: https://crash-stats.mozilla.com/report/list?signature=Abort%20%7C%20mozalloc_abort%20%7C%20NS_DebugBreak%20%7C%20nsDebugImpl%3A%3AAbort%20%7C%20NS_InvokeByIndex#tab-comments

Comment 1

2 years ago
i think this is just a signature change for the various asynchronous shutdown crashes that are handled in various bugs: 1255745 1273770 1255737 1258350 1255977
Track this as there is a high volume for 48 beta.
status-firefox50: --- → affected
tracking-firefox48: ? → +
tracking-firefox49: --- → +
tracking-firefox50: --- → +
Hi Kan-Ru,
May I have your help on this?
Flags: needinfo?(kchen)

Comment 4

2 years ago
this signature is a pool for many different async shutdown timeout crashes. probably it's better to close this bug and track the individual bugs that got filed for the different particular issues.
you get an idea of the different underlying issues when faceting those crashes by the "async shutdown timeout" field:
https://crash-stats.mozilla.com/search/?signature=%3DAbort%20|%20mozalloc_abort%20|%20NS_DebugBreak%20|%20nsDebugImpl%3A%3AAbort%20|%20NS_InvokeByIndex&_sort=-date&_facets=signature&_facets=version&_facets=async_shutdown_timeout#facet-async_shutdown_timeout

about 50% of them are due to "{"phase":"Places Clients shutdown","conditions":[]}" which is handled in bug 1258350.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(kchen)
Resolution: --- → INCOMPLETE
(In reply to [:philipp] from comment #4)
> this signature is a pool for many different async shutdown timeout crashes.
> probably it's better to close this bug and track the individual bugs that
> got filed for the different particular issues.
> you get an idea of the different underlying issues when faceting those
> crashes by the "async shutdown timeout" field:
> https://crash-stats.mozilla.com/search/
> ?signature=%3DAbort%20|%20mozalloc_abort%20|%20NS_DebugBreak%20|%20nsDebugImp
> l%3A%3AAbort%20|%20NS_InvokeByIndex&_sort=-
> date&_facets=signature&_facets=version&_facets=async_shutdown_timeout#facet-
> async_shutdown_timeout
> 
> about 50% of them are due to "{"phase":"Places Clients
> shutdown","conditions":[]}" which is handled in bug 1258350.

The crash above represents a much higher volume of crashes, so not sure it is worth filing some of the other ones since they are much lower volume.

Comment 7

2 years ago
thanks a lot.
status-firefox47: affected → wontfix
status-firefox48: affected → wontfix
status-firefox49: affected → fix-optional
status-firefox50: affected → fix-optional
You need to log in before you can comment on or make changes to this bug.