Crashes due to AMD OpenCL when working with pictures

NEW
Unassigned

Status

External Software Affecting Firefox
Other
P3
critical
a year ago
3 months ago

People

(Reporter: philipp, Unassigned)

Tracking

({crash})

unspecified
All
Windows
crash

Firefox Tracking Flags

(firefox-esr45 affected, firefox50 wontfix, firefox51 wontfix, firefox52 wontfix, firefox-esr52 wontfix, firefox53 wontfix, firefox56 wontfix, firefox57 wontfix, firefox58 affected)

Details

(crash signature)

(Reporter)

Description

a year ago
This bug was filed from the Socorro interface and is 
report bp-7db0e6f7-ead4-43e1-a2f7-127932161128.
=============================================================

there is a number of crash reports with signatures containing references to the amdocl*.dll module - they are spread out among various signatures (attaching the most common ones to the bug report).
these crashes mainly affect windows 10, windows 7 and windows 8.1 and have been going on for a while - they are happening on 32bit and 64bit builds.

many comments of affected users indicate that they where somehow interacting with pictures (downloading, uploading, copying...): http://bit.ly/2hVuiUS

some of those reports like https://crash-stats.mozilla.com/report/index/b6d53bcd-66a9-4017-a57e-1c4f52170102 have the amd related module amf-wic-jpeg-decoder64.dll in the stack, so it might also be related...

The ids of the most affected amd graphics adapters are:
1 	0x9874 	536 	28.66 %
2 	0x6611 	191 	10.21 %
3 	0x9851 	159 	8.50 %
4 	0x675f 	107 	5.72 %
5 	0x9830 	75 	4.01 %

Comment 1

a year ago
The drivers where this issue occurs are long outdated, any driver released since mid-last year should address the problem. The root cause is in the amf-wic-jpeg-decoder*.dll. Recommended update is to the Crimson ReLive Edition 16.12.x or newer.
Is this something we can work around? (other than suggesting users to update)
Too late for firefox 52, mass-wontfix.
status-firefox52: affected → wontfix

Comment 4

3 months ago
blocklist candidate. every version of this has issues, we should just eject all of them.
Priority: -- → P3
Duplicate of this bug: 1403741
Crash Signature: [@ amdocl.dll@0x23507b] [@ amdocl12cl.dll@0xd7f2] [@ amdocl12cl.dll@0xe31e] [@ amdocl64.dll@0x2a7230] [@ amdocl.dll@0x23563b] [@ amdocl.dll@0x234d0b] [@ amdocl12cl.dll@0xe34e] [@ amdocl.dll@0xbd7e] [@ amdocl.dll@0x18d794] [@ amdocl.dll@0x2… → [@ amdocl.dll@0x23507b] [@ amdocl12cl.dll@0xd7f2] [@ amdocl12cl.dll@0xe31e] [@ amdocl64.dll@0x2a7230] [@ amdocl.dll@0x23563b] [@ amdocl.dll@0x234d0b] [@ amdocl12cl.dll@0xe34e] [@ amdocl.dll@0xbd7e] [@ amdocl.dll@0x18d794] [@ amdocl.dll@0x2…
(In reply to kyle.plumadore from bug 1403741 comment 4)
> 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.

(In reply to Jim Mathies [:jimm] from comment #4)
> blocklist candidate. every version of this has issues, we should just eject
> all of them.

I'm afraid if we blocked these DLLs regardless of version we could prevent VP9 decoding acceleration from working for some users.
Low crash volume, wontfix for 57.
status-firefox50: affected → wontfix
status-firefox51: affected → wontfix
status-firefox53: affected → wontfix
status-firefox56: --- → wontfix
status-firefox57: --- → wontfix
status-firefox58: --- → affected
status-firefox-esr52: --- → wontfix
You need to log in before you can comment on or make changes to this bug.