crash in aticfx32.dll@0x25861 mostly with Intel Ironlake

RESOLVED WORKSFORME

Status

()

Core
Graphics
--
critical
RESOLVED WORKSFORME
3 years ago
2 years ago

People

(Reporter: ashughes, Unassigned)

Tracking

({crash})

41 Branch
x86
Windows 7
crash
Points:
---

Firefox Tracking Flags

(platform-rel ?, firefox42- wontfix)

Details

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

(Reporter)

Description

3 years ago
This bug was filed from the Socorro interface and is 
report bp-322c0412-b84c-4b8f-82c0-df75f2151117.
=============================================================
 	Module 	Signature 	Source
Ø 0 	aticfx32.dll 	aticfx32.dll@0x25861 	
Ø 1 	aticfx32.dll 	aticfx32.dll@0x23f2b 	
Ø 2 	atigktxx.dll 	atigktxx.dll@0x1dae 	
Ø 3 	ig4icd32.dll 	ig4icd32.dll@0x56d351 	
Ø 4 	ig4icd32.dll 	ig4icd32.dll@0x56265b 	=============================================================
https://crash-stats.mozilla.com/report/list?product=Firefox&signature=aticfx32.dll%400x25861

Device Correlations:
99.28% Intel 0x0046 Core Processor GPU (ironlake)
 0.36% AMD 0x95c5 Radeon HD 3450 (RV620 LE)
 0.36% Intel 0x0102 2nd-Gen Core Processor GPU (sandybridge-gt1)

Driver Correlations:
1 	8.15.10.2189 	300 	98.68 %
2 	8.15.10.2253 	2 	0.66 %
3 	8.15.10.2182 	1 	0.33 %
4 	8.56.1.16 	1 	0.33 %
(Reporter)

Comment 1

3 years ago
[Tracking Requested - why for this release]: not a topcrash but seems highly correlated to a specific device/driver configuration so may be a blacklist candidate. Crashes are exclusively on Windows 7 and mostly on Firefox 42, although crashes seemed to start with Firefox 41. Shows up highly explosive in https://crash-analysis.mozilla.com/rkaiser/2015-11-16/2015-11-16.firefox.release.explosiveness.html.
status-firefox42: --- → affected
tracking-firefox42: --- → ?
(Reporter)

Comment 2

3 years ago
Milan, not sure who is best to look in to this.
Flags: needinfo?(milan)
Whiteboard: gfx-noted
status-firefox42: affected → wontfix
tracking-firefox42: ? → -
No crashes since 42 with this exact signature.  This looks like Intel driver (ig4icd32.dll) calling ATI driver (aticfx32.dll).  I'm seeing 8 of these total, which could be because it's driver version specific, except that those 8 are the only ones with the aticfx32.dll/ig4icd32.dll combination.  All of them are on Intel driver version 8.15.10.2189 and device 0x0046, so it's possible we're internally blocking something as of 43.

aticfx32.dll on its own show up the most in the address supposedly handled by bug 1099252.
Flags: needinfo?(milan)
Whiteboard: gfx-noted → gfx-noted [platform-rel-Intel]

Updated

2 years ago
platform-rel: --- → ?
Only seven crashes, 41-43, that have both aticfx32.dll and ig4icd32.dll in the signature.  Closing.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.