Closed Bug 786076 Opened 7 years ago Closed 3 years ago
Firefox crash in igd10umd32 with Intel driver version 8
.15 .10 .2342 and HD Graphics based on Sandy Bridge
This bug was filed from the Socorro interface and is report bp-7d051055-2ab1-4bc6-b601-094592120827 . ============================================================= Seen while looking at Win 8 crash stats. This one seems to be correlated to Intel HD Graphics 220.127.116.112. Happens on Windows 7 as well in smaller volume. https://crash-stats.mozilla.com/report/list?signature=%20igd10umd32.dll@0xe33c1 Frame Module Signature Source 0 igd10umd32.dll igd10umd32.dll@0xe33c1 1 igd10umd32.dll igd10umd32.dll@0xf92cd 2 igd10umd32.dll igd10umd32.dll@0xf9c57 3 igd10umd32.dll igd10umd32.dll@0xe60d5 4 igd10umd32.dll igd10umd32.dll@0xe1673 5 igd10umd32.dll igd10umd32.dll@0x13b1f 6 igd10umd32.dll igd10umd32.dll@0x13d21 7 igd10umd32.dll igd10umd32.dll@0x62e6 8 igd10umd32.dll igd10umd32.dll@0x24b7b 9 igd10umd32.dll igd10umd32.dll@0x269c9
Device ids are 106, 116, 126, which are HD Graphics based on SandyBridge. The current driver version is 18.104.22.16822 and the driver version released after 22.214.171.1242 is 126.96.36.1991. IntelGMAX4500HD should be divide in two parts (see https://en.wikipedia.org/wiki/Comparison_of_Intel_graphics_processing_units#Intel_HD_Graphics).
Depends on: 706908
Summary: Firefox crash in igd10umd32 [Intel 188.8.131.522] → Firefox crash in igd10umd32 with Intel driver version 184.108.40.2062 and HD Graphics based on Sandy Bridge
(In reply to Scoobidiver from comment #1) > Device ids are 106, 116, 126, which are HD Graphics based on SandyBridge. > > The current driver version is 220.127.116.1122 and the driver version released > after 18.104.22.1682 is 22.214.171.1241. > not so, Scoobidiver. shouldn't the "current" driver version be 126.96.36.19961 for SandyBridge Intel HD Graphics chipsets? at least, that's the latest official version from Intel: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=21476&lang=eng
(In reply to erpman1 from comment #2) > not so, Scoobidiver. shouldn't the "current" driver version be 188.8.131.5261 > for SandyBridge Intel HD Graphics chipsets? We try to ensure HW acceleration to most people, not only those who have the latest version when we have decided to blocklist.
one of the topcrashers for win8(https://crash-analysis.mozilla.com/chofmann/20120904/top-winNT-crashes-details.txt).Bas, can you please take a look or offer recommendation for reproducing this issue
After conversing with Bas on this, he seemed sure its not that big of an issue.Based on that we can untrack this for FF16 and revisit if its get's worse or have any other leads .
(In reply to bhavana bajaj [:bajaj] from comment #5) > After conversing with Bas on this, he seemed sure its not that big of an > issue.Based on that we can untrack this for FF16 and revisit if its get's > worse or have any other leads . Did we ever get the statistics with relation to this crash we discussed?
Bas below are the stats at my end , let us know how you want to go about this : So looking at : https://crash-stats.mozilla.com/report/list?product=Firefox&query_search=signature&query_type=exact&query=igd10umd32.dll%400xe33c1&reason_type=contains&date=09%2F17%2F2012%2019%3A36%3A28&range_value=2&range_unit=weeks&hang_type=any&process_type=any&do_query=1&signature=igd10umd32.dll%400xe33c1 I think the population of users crashing on win7 is way less than on win8 for the same signature, hence i would say its more of a win8 issue . Also I do not see this bug in top 100 crashes reported at https://crash-analysis.mozilla.com/chofmann/20120916/top-winNT-crashes-details.txt for win7 (6.1) but it in top 10 for win8 (6.2).
Let's retrack for FF17 if this ends up being a major issue once Win8 is released.
The downloaded graphics blocklist can be used at any time for every channels if the Win 8 release confirms it's a top crasher.
It's #26 top crasher for Windows 8 only in 17.0.
3 years ago
Whiteboard: [Win8] → [Win8] [platform-rel-Intel]
3 years ago
platform-rel: ? → ---
I'm marking this bug as WORKSFORME as bug crashlog signature didn't appear from a long time (over half year) in Firefox.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.