Crash in [@ NS_TableDrivenQI]
Categories
(Core :: XPCOM, defect)
Tracking
()
People
(Reporter: marcia, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: crash, Whiteboard: [startupcrash])
Crash Data
Comment 1•15 years ago
|
||
Updated•15 years ago
|
Comment 2•15 years ago
|
||
| Reporter | ||
Updated•15 years ago
|
Comment 3•15 years ago
|
||
| Assignee | ||
Updated•15 years ago
|
Updated•10 years ago
|
Comment 5•9 years ago
|
||
Comment 6•9 years ago
|
||
Comment 7•9 years ago
|
||
Comment 8•9 years ago
|
||
Comment 9•9 years ago
|
||
Comment 10•9 years ago
|
||
Comment 11•5 years ago
|
||
I doubt the bulk of crashes, few that they are (<90/week for Firefox), are actionable. bp-73534204-552a-4732-a98f-1ff910210220, 0 seconds, is an example.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 12•3 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on release (startup)
For more information, please visit auto_nag documentation.
Comment 13•3 years ago
|
||
This has spiked up, but it looks entirely due to a single installation that has crashes more than 400 times.
Here's one of those crashes: bp-7b6e4d72-b628-4ce8-b123-b2d900230404
The stack has nsInputStreamChannel::QueryInterface(), but not much else.
Comment 14•3 years ago
|
||
This seems unactionable, and like we should perhaps just add it to the prefix list.
Comment 15•3 years ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit auto_nag documentation.
| Comment hidden (Intermittent Failures Robot) |
Comment 17•3 months ago
|
||
Triaging this crash bug for current actionability.
Volume (last 90 days): ~276 crash reports, ~185 crash pings. However, ~67 of those reports come from a single Firefox 130.0.1 installation crashing repeatedly, and the remainder are spread across dozens of completely different call stacks.
Bucket signature confirmed: Examining individual crashes confirms what benjamin noted in comment 3 and nika in comment 14 — this is a generic XPCOM QI dispatch function that groups unrelated crashes. The proto_signature facet shows 25+ distinct call paths, including:
nsMediaSniffer::QueryInterfacevia HTTP channel processingnsNSSCertificate::QueryInterfacevia cache entry handlingMessageChannel::MessageTask::QueryInterfaceon IPC I/O thread- Many truncated/corrupted stacks with no useful callers
The largest individual cluster is ~7 crashes — none individually actionable from this bug.
NS_TableDrivenQI (source) is not currently in Socorro's prefix_signature_re.txt. Adding it would cause Socorro to generate more specific signatures (e.g. nsMediaSniffer::QueryInterface) so individual root causes get their own bugs instead of being lumped here.
Recommendation: File a Socorro bug to add NS_TableDrivenQI to the prefix list. Once that lands, this bug will stop accumulating new crashes and can be closed. The topcrash/topcrash-startup keywords should be removed as the volume is an artifact of the bucket effect.
Description
•