INVALID_READ crashes involving addresses in 0xffffff... with ATI drivers

RESOLVED INCOMPLETE

Status

()

Core
Graphics
--
critical
RESOLVED INCOMPLETE
8 years ago
2 years ago

People

(Reporter: bjacob, Unassigned)

Tracking

(Blocks: 1 bug, {crash})

Trunk
x86
Windows 7
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

http://crash-stats.mozilla.com/report/index/f40c6c8c-b1cf-4987-849d-7277c2101020
This is Win7, Evergreen device, Catalyst 9.11 (atidxx32.dll 8.17.10.240)
Signature: atidxx32.dll@0x79947
Crash reason: ACCESS_VIOLATION_READ at 0xffffffffffffffff


http://crash-stats.mozilla.com/report/index/cd14e7b0-da04-4492-b776-e00522101018
This is Win7, Radeon HD 5470 device, Catalyst 10.1 (atidxx32.dll 8.17.10.252)
Signature: atidxx32.dll@0x95455
Crash reason: ACCESS_VIOLATION_READ at 0x2c
Notice the @0xfffffffe calling frame 1, in the stack trace.

If we get more similar crashes AND NOT on current driver version, we should
blacklist these old driver versions.
(Reporter)

Comment 1

8 years ago
http://crash-stats.mozilla.com/report/index/41b435c1-8c33-4323-a571-230742101018
Win7, device: R710
Signature: atidxx32.dll@0x8be66
ACCESS_VIOLATION_READ at 0xffffffffffffff8f
(Reporter)

Comment 2

8 years ago
The crash in comment 1 is with Catalyst 10.3 (atidxx32.dll 8.17.10.261)

Comment 4

7 years ago
Here are a couple recent examples:
https://crash-stats.mozilla.com/report/index/5719b764-a85a-4080-9aa2-19fbc2111102
(driver version 8.741.0.0)

https://crash-stats.mozilla.com/report/index/c1826a63-7451-45b1-a242-7e0ae2111116
(driver version 8.902.0.0)

Note that 8.902 = Catalyst 11.10, which is only a few weeks old, so this isn't just happening in old drivers.
Summary: INVALID_READ crashes involving addresses in 0xffffff... with old ATI drivers → INVALID_READ crashes involving addresses in 0xffffff... with ATI drivers

Updated

7 years ago
Severity: normal → critical
Crash Signature: [@ atidxx32.dll@0x79947 ] [@ atidxx32.dll@0x95455 ] [@ atidxx32.dll@0x8be66 ]
Keywords: crash
I'm closing this bug as incomplete. There are a couple of reports on the latest release with pretty old AMD hardware/drivers. If someone has some leads and wants to try fixing this then please reopen.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.