If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

crash in nsUrlClassifierPrefixSet::MakePrefixSet(unsigned int const*, unsigned int)

NEW
Unassigned

Status

()

Toolkit
Safe Browsing
P5
normal
2 years ago
8 months ago

People

(Reporter: Ehsan, Unassigned)

Tracking

({crash})

unspecified
Unspecified
Mac OS X
crash
Points:
---

Firefox Tracking Flags

(firefox47 affected, firefox48 affected)

Details

(crash signature)

This bug was filed from the Socorro interface and is 
report bp-c321cc57-bdab-490c-9db9-c395a2150828.
=============================================================
Nothing usable in the stack trace. Is this reproducible with a certain profile?
No, I have hit it once so far, I think.

Updated

2 years ago
Crash Signature: [@ nsUrlClassifierPrefixSet::MakePrefixSet(unsigned int const*, unsigned int)] → [@ nsUrlClassifierPrefixSet::MakePrefixSet(unsigned int const*, unsigned int)] [@ nsUrlClassifierPrefixSet::MakePrefixSet]
Crash volume for signature 'nsUrlClassifierPrefixSet::MakePrefixSet':
 - nightly (version 50): 0 crash from 2016-06-06.
 - aurora  (version 49): 0 crash from 2016-06-07.
 - beta    (version 48): 17 crashes from 2016-06-06.
 - release (version 47): 12 crashes from 2016-05-31.
 - esr     (version 45): 0 crash from 2016-04-07.

Crash volume on the last weeks:
             Week N-1   Week N-2   Week N-3   Week N-4   Week N-5   Week N-6   Week N-7
 - nightly          0          0          0          0          0          0          0
 - aurora           0          0          0          0          0          0          0
 - beta             1          0         16          0          0          0          0
 - release          1          5          2          1          1          1          0
 - esr              0          0          0          0          0          0          0

Affected platform: Windows
status-firefox47: --- → affected
status-firefox48: --- → affected
Seems like it's mostly happening on Fennec: https://crash-stats.mozilla.com/signature/?signature=nsUrlClassifierPrefixSet%3A%3AMakePrefixSet&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_sort=-date&page=1#reports

Which won't be a problem anymore once we move to the new V4 API for Android.
Severity: critical → normal
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.