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 OOM | large | mozalloc_abort | mozalloc_handle_oom | moz_xrealloc | winWrite

NEW
Unassigned

Status

()

Toolkit
Storage
P3
critical
a year ago
a year ago

People

(Reporter: njn, Unassigned)

Tracking

({crash})

unspecified
x86
Windows Vista
crash
Points:
---

Firefox Tracking Flags

(firefox47 affected)

Details

(crash signature)

(Reporter)

Description

a year ago
This bug was filed from the Socorro interface and is 
report bp-23d23587-74bf-4700-9547-e54272160729.
=============================================================

This is the #61 topcrash signature on 47.0.1. It's a weird one. winWrite is a function in SQLite that doesn't do any allocation, AFAICT. The line being blamed in the crash reports is a call to memset(), which is clearly bogus. I looked at a minidump in MSVC and the stack trace it gave looked like this:

> mozalloc_abort
> mozalloc_handle_oom
> moz_xrealloc
> [External code]
> [Frames below may be incorrect and/or missing]
> nsThread::ProcessNextEvent
> etc.

My best guess is that the actual cause of the OOM correlates with calls to winWrite somehow.
Crash volume for signature 'OOM | large | mozalloc_abort | mozalloc_handle_oom | moz_xrealloc | winWrite':
 - nightly(version 50):0 crashes from 2016-06-06.
 - aurora (version 49):0 crashes from 2016-06-07.
 - beta   (version 48):0 crashes from 2016-06-06.
 - release(version 47):1142 crashes from 2016-05-31.
 - esr    (version 45):0 crashes from 2016-04-07.

Crash volume on the last weeks:
            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     346     293     240     159      89       0       0
 - esr           0       0       0       0       0       0       0

Affected platform: Windows
status-firefox47: --- → affected
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.