Closed Bug 1380798 Opened 8 years ago Closed 6 years ago

Crash in OOM | large | mozalloc_abort | mozalloc_handle_oom | moz_xmalloc | std::_Allocate | std::vector<T>::_Reserve

Categories

(Core :: Graphics, defect, P5)

Product:
Core
Component:
Graphics
Platform:
Unspecified
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox57 --- fix-optional

People

(Reporter: mccr8, Unassigned)

Details

(Keywords: crash, Whiteboard: gfx-noted)

Crash Data

This bug was filed from the Socorro interface and is report bp-5a9f903b-946f-4f4d-8c66-da2dd0170710. ============================================================= These crashes are happening inside rx::d3d11::GenerateInitialTextureData(). There are 113 crashes with this signature in the last 7 days (all on Nightly), which is quite a few, but that's from only 3 installations. I don't know why so many crash reports are being generated.
58 crashes for 20170717030207 build but from only 1 installation.
All the crashes are mainly from 3 installation, maybe we can monitor this for a little while more and see if there are more crash reports.
Whiteboard: gfx-noted
In the crash report from comment 0, there's about 140MB of available physical memory. I suspect somebody is running Firefox in an automated fashion in a VM, with very restricted memory.

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.