Open Bug 1260703 Opened 10 years ago Updated 3 years ago

OOM crash allocating a texture using D3D11

Categories

(Core :: Graphics, defect, P3)

All
Windows 10
defect

Tracking

()

People

(Reporter: padenot, Unassigned)

Details

(Whiteboard: gfx-noted)

Attachments

(2 files)

Attached file stacks-and-args —
Got this running `./mach crashtest dom/media` in a debug build on hg revision d5d53a3b4e50, stacks and arguments attached. This is on a Windows 10 / Thinkpad w520 machine, gfx section of about:support also attached. I saved a minidump locally if needed. `hr` is `E_OUTOFMEMORY`, that must be GPU memory because I've got plenty of ram left (at least 10GB) and the process resident size is like 350MB.
Attached file about:support —
Can you reproduce it reliably?
Flags: needinfo?(padenot)
Nope, sorry, this was a one off, but I got a full-heap dump.
Flags: needinfo?(padenot)
Whiteboard: gfx-noted
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: