Closed Bug 1403741 Opened 7 years ago Closed 7 years ago

Crash in amdocl64.dll@0x43d56

Categories

(Core :: Audio/Video: Playback, defect, P2)

Product:
Core
Component:
Audio/Video: Playback
Version:
57 Branch
Platform:
x86_64
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1328838
Tracking Flags:
Tracking Status
firefox57 --- fix-optional
firefox58 --- wontfix

People

(Reporter: philipp, Unassigned)

Details

(Keywords: crash, regression) 

This bug was filed from the Socorro interface and is 
report bp-3333f398-bbe7-42ef-8588-b2ddf0170927.
=============================================================
Crashing Thread (72), Name: MediaPlayback #2
Frame 	Module 	Signature 	Source
Ø 0 	amdocl64.dll 	amdocl64.dll@0x43d56 	
Ø 1 	amdocl64.dll 	amdocl64.dll@0x21f8c2 	
Ø 2 	amdocl64.dll 	amdocl64.dll@0x21b2ac 	
Ø 3 	amdocl64.dll 	amdocl64.dll@0x1cf233 	
Ø 4 	amf-mft-decvp9-decoder64.dll 	amf-mft-decvp9-decoder64.dll@0x4e88a 	
5 	kernelbase.dll 	InitOnceExecuteOnce

crashes with amdocl64.dll on windows 10 are increasing with 57, though still on a rather low level till now. app notes in the crash reports suggest that it's happening during DXVA2D3D11 media playback.
Jya, 
Is it related to AMD driver?
Component: Audio/Video → Audio/Video: Playback
Flags: needinfo?(jyavenard)
Priority: -- → P2
Must be. This is the AMD VP9 decoder...
Flags: needinfo?(jyavenard)
Kyle.

Does this ring any bells?
Flags: needinfo?(kyle.plumadore)
This looks like a corrupt OpenCL installation on the system. This hardware doesn't support the amd vp9 decoder, but the amdopencl driver will still be loaded to query the hardware name. It appears as if this basic opencl query is crashing in the amd opencl driver, likely due to some mismatch of opencl components.

My guess would be that this happened due to the user doing something "abnormal" e.g. partly installing amd drivers, or installing an old opencl driver on top of a newer driver. We've seen similar crashes when users manually install the AMD APP development sdk, which comes with it's own version of amdocl64.dll. (We actually shipped a workaround for this case in a more recent driver version)

I don't suppose we have access to a failing system to get more info? I would be interested to know whether doing something as simple as opening a command prompt and typing "clinfo" would also crash. It would also be interesting to know the full path of the amdopencl64.dll module that's loaded into the firefox process.
Flags: needinfo?(kyle.plumadore)
In any case I'll try to repro to double check that it's not actually a generic issue.
I don't see any crashes when I play a vp9 video on on the same hardware.
Status: NEW → RESOLVED
Crash Signature: [@ amdocl64.dll@0x43d56] [@ amdocl64.dll@0x478c6] [@ amdocl64.dll@0x478d6]
Closed: 7 years ago
Resolution: --- → DUPLICATE
Wontfixed in the duplicate for 58 so I'm doing the same here.
status-firefox58: affected → wontfix
You need to log in before you can comment on or make changes to this bug.