Crash in igd10iumd32.dll | CContext::ID3D11DeviceContext1_UpdateSubresource_<T> in during AttemptDeviceCreation

NEW
Unassigned

Status

()

Core
Graphics
P3
critical
2 years ago
10 months ago

People

(Reporter: jrmuizel, Unassigned)

Tracking

({crash})

unspecified
crash
Points:
---

Firefox Tracking Flags

(firefox48 affected, firefox49 affected, firefox-esr45 affected, firefox50 affected, firefox51 affected, firefox52 wontfix)

Details

(Whiteboard: gfx-noted, crash signature)

(Reporter)

Description

2 years ago
https://crash-stats.mozilla.com/report/index/e91de4de-5f04-43d7-a399-d18cf2160623

This seems to mostly happen on device reset after things have gone wrong. (GfxCriticalError seems to have lots of things going bad)
(Reporter)

Updated

2 years ago
Crash Signature: [@ igd10iumd32.dll | CContext::ID3D11DeviceContext1_UpdateSubresource_<T> ]
See Also: → bug 1282562
Whiteboard: gfx-noted
Are crashes in [@ igd10iumd32.dll | CResource<T>::CopySubresourceRegion<T>] related to this?
https://crash-stats.mozilla.com/report/list?signature=igd10iumd32.dll | CResource<T>%3A%3ACopySubresourceRegion<T>
The following search indicates that this is OOM-related:

https://crash-stats.mozilla.com/search/?signature=%3Digd10iumd32.dll%20%7C%20CContext%3A%3AID3D11DeviceContext1_UpdateSubresource_%3CT%3E&_sort=-date&_facets=signature&_facets=contains_memory_report&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-contains_memory_report

Of the 1544 occurrences of crashes with the signature "[@ nsWindow::ClearTranslucent]" in the past 7 days, 1145 (74.2%) of them have a ContainsMemoryReport=1 field, which indicates that memory was low near the time of crash. (See the "Contains memory report" facet in the search output.)

Perhaps we're failing to check the result of an operation that allocates?
Crash volume for signature 'igd10iumd32.dll | CContext::ID3D11DeviceContext1_UpdateSubresource_<T>':
 - nightly (version 50): 2 crashes from 2016-06-06.
 - aurora  (version 49): 7 crashes from 2016-06-07.
 - beta    (version 48): 1096 crashes from 2016-06-06.
 - release (version 47): 6128 crashes from 2016-05-31.
 - esr     (version 45): 1441 crashes from 2016-04-07.

Crash volume on the last weeks:
            W. N-1  W. N-2  W. N-3  W. N-4  W. N-5  W. N-6  W. N-7
 - nightly       0       0       0       1       1       0       0
 - aurora        1       0       1       2       3       0       0
 - beta        183     201     177     166     219     101       0
 - release    1037    1147    1081     994    1125     561       0
 - esr         283     242     276     220     247     132       0

Affected platform: Windows
status-firefox48: --- → affected
status-firefox49: --- → affected
status-firefox50: --- → affected
status-firefox-esr45: --- → affected

Updated

2 years ago
Severity: normal → critical
Keywords: crash
(99.59% in signature vs 09.04% overall) reason = EXCEPTION_ACCESS_VIOLATION_WRITE
(92.65% in signature vs 10.86% overall) address = 0x0
(85.31% in signature vs 07.79% overall) GFX_ERROR "[D3D11] " = true
(71.43% in signature vs 10.41% overall) contains_memory_report = 1
(95.51% in signature vs 39.22% overall) platform_version = 6.1.7601 Service Pack 1
(60.82% in signature vs 06.87% overall) GFX_ERROR "Failed 2 buffer db=" = true
(100.0% in signature vs 49.04% overall) adapter_vendor_id = 0x8086
(95.51% in signature vs 46.44% overall) platform_pretty_version = Windows 7
(51.02% in signature vs 03.75% overall) GFX_ERROR "[D2D1.1] 4CreateBitmap failure " = true
(34.69% in signature vs 04.16% overall) cpu_info = GenuineIntel family 6 model 60 stepping 3 | 4
(29.80% in signature vs 00.56% overall) adapter_driver_version = 10.18.10.3412
(29.80% in signature vs 00.60% overall) GFX_ERROR "Failed to D3D11 OpenSharedResource for frame finalization: " = true
(24.49% in signature vs 00.59% overall) graphics_startup_test = 1
(24.49% in signature vs 01.33% overall) adapter_device_id = 0x0412
(25.31% in signature vs 00.29% overall) GFX_ERROR "Failed 2 buffer db=" = true ∧ GFX_ERROR "Failed to D3D11 OpenSharedResource for frame finalization: " = true
(21.22% in signature vs 00.15% overall) contains_memory_report = 1 ∧ graphics_startup_test = 1

Quite similar correlations to bug 1282562.
Crash volume for signature 'igd10iumd32.dll | CContext::ID3D11DeviceContext1_UpdateSubresource_<T>':
 - nightly (version 52): 0 crashes from 2016-09-19.
 - aurora  (version 51): 1 crash from 2016-09-19.
 - beta    (version 50): 167 crashes from 2016-09-20.
 - release (version 49): 710 crashes from 2016-09-05.
 - esr     (version 45): 3694 crashes from 2016-06-01.

Crash volume on the last weeks (Week N is from 10-03 to 10-09):
            W. N-1  W. N-2
 - nightly       0       0
 - aurora        1       0
 - beta        138      29
 - release     595     115
 - esr         305     321

Affected platform: Windows

Crash rank on the last 7 days:
           Browser   Content     Plugin
 - nightly
 - aurora  #1320
 - beta    #116
 - release #81       #421
 - esr     #31
status-firefox51: --- → affected
(In reply to Nicholas Nethercote [:njn] from comment #2)
> The following search indicates that this is OOM-related:
> 

Are we seeing a corresponding drop in other OOM crashes?  In other words, are we seeing more OOMs (assuming this is one of them), or we're now seeing some OOMs transferred into these signatures?
Flags: needinfo?(n.nethercote)
Crash volume for signature 'igd10iumd32.dll | CContext::ID3D11DeviceContext1_UpdateSubresource_<T>':
 - nightly (version 52): 1 crash from 2016-09-19.
 - aurora  (version 51): 2 crashes from 2016-09-19.
 - beta    (version 50): 510 crashes from 2016-09-20.
 - release (version 49): 2310 crashes from 2016-09-05.
 - esr     (version 45): 2710 crashes from 2016-07-25.

Crash volume on the last weeks (Week N is from 10-17 to 10-23):
            W. N-1  W. N-2  W. N-3  W. N-4
 - nightly       0       0       0       0
 - aurora        0       1       1       0
 - beta        128     168     138      29
 - release     718     641     596     115
 - esr         321     304     272     301

Affected platform: Windows

Crash rank on the last 7 days:
           Browser   Content     Plugin
 - nightly #705
 - aurora
 - beta    #116      #966
 - release #76       #360
 - esr     #28
status-firefox52: --- → affected
> Are we seeing a corresponding drop in other OOM crashes?  In other words,
> are we seeing more OOMs (assuming this is one of them), or we're now seeing
> some OOMs transferred into these signatures?

I haven't seen any notable changes in other OOM crashes.

(Apologies for the slow response.)
Flags: needinfo?(n.nethercote)
Too late for firefox 52, mass-wontfix.
status-firefox52: affected → wontfix
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.