Closed Bug 1329756 Opened 7 years ago Closed 7 years ago

Crash in OOM | large | NS_ABORT_OOM | nsACString_internal::Assign | nsRefPtrHashtable<T>::Get | mozilla::dom::workers::ServiceWorkerManager::GetDocumentRegistration

Categories

(Core :: DOM: Service Workers, defect, P2)

x86
Windows 8
defect

Tracking

()

RESOLVED FIXED
Tracking Status
firefox50 --- affected

People

(Reporter: bkelly, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-4501f57e-4fc1-4f36-bdd2-e9fe32161219.
=============================================================

We are hitting some strange large OOM crashes from image loading.  The ImageCacheKey is trying to find out if it has a controlled document or not by using SWM.  The stack claims we are blowing up inside the SWM hash lookup.

The weird thing is, though, it also claims we are using strings, but we are not.

About 700 crashes in the last month.
Crash volume for signature 'OOM | large | NS_ABORT_OOM | nsACString_internal::Assign | nsRefPtrHashtable<T>::Get | mozilla::dom::workers::ServiceWorkerManager::GetDocumentRegistration':
 - nightly (version 53): 0 crashes from 2016-11-14.
 - aurora  (version 52): 0 crashes from 2016-11-14.
 - beta    (version 51): 0 crashes from 2016-11-14.
 - release (version 50): 1244 crashes from 2016-11-01.
 - esr     (version 45): 0 crashes from 2016-07-13.

Crash volume on the last weeks (Week N is from 01-09 to 01-15):
            W. N-1  W. N-2  W. N-3  W. N-4  W. N-5  W. N-6  W. N-7
 - nightly       0       0       0       0       0       0       0
 - aurora        0       0       0       0       0       0       0
 - beta          0       0       0       0       0       0       0
 - release     159     158     182     172     177     180     146
 - esr           0       0       0       0       0       0       0

Affected platform: Windows

Crash rank on the last 7 days:
           Browser   Content   Plugin
 - nightly
 - aurora
 - beta
 - release #391      #569
 - esr
I think we should see what happens when bug 1320196 merges to release channel in a couple weeks.  Its possible this is the same crash but the stacks are confused.
Depends on: 1320196
Priority: -- → P2
Bug 1297300 might have affected this too, it also landed on the 51 train.
Haven't seen the crash report for a long while. Free free to reopen it if the issue is still valid.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.