WebGl crash @ d3dcompiler_47.dll@0xd7825

UNCONFIRMED
Unassigned

Status

()

Core
Canvas: WebGL
P3
critical
UNCONFIRMED
8 months ago
5 months ago

People

(Reporter: Aral Yaman, Unassigned)

Tracking

({crash})

55 Branch
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gfx-noted], crash signature)

Attachments

(1 attachment)

(Reporter)

Description

8 months ago
Created attachment 8858593 [details]
crash.html

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170415030205

Steps to reproduce:

Open crash.html




Actual results:

Firefox crashes after linking the compiled shader program.

Here is the crash report:
https://crash-stats.mozilla.com/report/index/ded6acbf-52ea-4580-85f5-e26f92170416







Expected results:

No Crash see other browsers like chrome.

Updated

8 months ago
Severity: normal → critical
Crash Signature: [@ d3dcompiler_47.dll@0xd7825 ]
Component: Untriaged → Canvas: WebGL
Keywords: crash
Product: Firefox → Core
From the crashstat, it seems to happen on Haswell-based CPU with HD4400.

And I cannot reproduce this crash on an Ivybridge-based CPU with HD4000.

I suspect it is another driver issue.
I can't reproduce it on my Intel HD6700 Win 10 as well.

Comment 3

8 months ago
I also can't reproduce this issue on my win-10 with Intel HD graphic card. Looked into the crash report, there were totally two crashes about to this. One was 52.0.2 and the other was 55.0a1. They all got the reason EXCEPTION_ACCESS_VIOLATION_READ, meaning that point access might became invalid. Since the back trace deeply in driver, there was no obvious clue to lead to root cause.
Whiteboard: [gfx-noted]
(Reporter)

Comment 4

8 months ago
I missed to mention that you have to disable Hardware Acceleration in the Firefox properties for triggering the crash.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.