crash @ igd10iumd32.dll@0x2a3a2

RESOLVED INCOMPLETE

Status

()

--
critical
RESOLVED INCOMPLETE
4 years ago
2 years ago

People

(Reporter: devotip, Unassigned, NeedInfo)

Tracking

({crash})

38 Branch
x86_64
Windows 7
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: gfx-noted, crash signature, URL)

Devoti: Can you please paste the crash ID from about:crashes (type that in the URL bar) Thanks.
Flags: needinfo?(devotip)

Comment 2

4 years ago
In addition, are you able to reproduce the crash:
1) in safe mode: https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
2) with a fresh profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
(Reporter)

Comment 3

4 years ago
crash IDs

bp-8956420d-e5ba-48ac-b863-29f612150609
	09/06/2015	16:30
bp-d0e46d22-41b6-4cfd-98f4-1d3da2150609
	09/06/2015	16:15
bp-7c44b401-d635-4f60-91ea-254302150609
	09/06/2015	16:09
bp-e4ec6d24-e735-4a0a-8396-b24e52150609
	09/06/2015	16:08
Flags: needinfo?(devotip)
(Reporter)

Comment 4

4 years ago
no cresh when in safe mode

Comment 5

4 years ago
Seems related to hardware acceleration. Please type about:support into the location bar, then press Enter. Click the “Copy text to clipboard” button, then paste the clipboard contents in a comment here.
Severity: normal → critical
Crash Signature: igd10iumd32.dll@0x2a3a2
Component: Untriaged → Graphics
Keywords: crash
OS: Unspecified → Windows 7
Product: Firefox → Core
Hardware: Unspecified → x86_64
Summary: crash when opening page → crash @ igd10iumd32.dll@0x2a3a2
(Reporter)

Comment 6

4 years ago
Informazioni di base
--------------------

Nome: Firefox
Versione: 38.0.5
ID build: 20150525141253
Canale di aggiornamento: release
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Finestre multiprocesso: 0/1 (predefinito: false)

Segnalazioni di arresto anomalo degli ultimi 3 giorni
-----------------------------------------------------

ID segnalazione: bp-8956420d-e5ba-48ac-b863-29f612150609
Inviata: 18 ore fa

ID segnalazione: bp-d0e46d22-41b6-4cfd-98f4-1d3da2150609
Inviata: 19 ore fa

ID segnalazione: bp-7c44b401-d635-4f60-91ea-254302150609
Inviata: 19 ore fa

ID segnalazione: bp-e4ec6d24-e735-4a0a-8396-b24e52150609
Inviata: 19 ore fa

ID segnalazione: bp-b0bb2666-c5fc-425e-8ee4-2e5dc2150609
Inviata: 19 ore fa

Tutte le segnalazioni

Estensioni
----------

Nome: HP Client Security Manager
Versione: 1.0.0.5952
Attiva: false
ID: dpmaxz_ng@jetpack

Grafica
-------

Data aggiornamento driver: 3-16-2015
Descrizione scheda grafica: Intel(R) HD Graphics 4600
Direct2D attivo: true
DirectWrite attivo: true (6.2.9200.17292)
Driver scheda grafica: igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
Finestre con accelerazione GPU: 1/1 Direct3D 11 (OMTC)
GPU #2 attiva: false
ID dispositivo: 0x0412
ID produttore: 0x8086
ID sottosistema: 21f5103c
RAM scheda grafica: Unknown
Rendering WebGL: Google Inc. -- ANGLE (Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0)
Versione driver: 10.18.14.4170
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

Preferenze importanti modificate
--------------------------------

accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.capacity: 358400
browser.cache.disk.smart_size.first_run: false
browser.cache.frecency_experiment: 2
browser.download.importedFromSqlite: true
browser.download.useDownloadDir: false
browser.fixup.domainwhitelist.iesweb: true
browser.places.smartBookmarksVersion: 7
browser.sessionstore.upgradeBackup.latestBuildID: 20150525141253
browser.startup.homepage_override.buildID: 20150525141253
browser.startup.homepage_override.mstone: 38.0.5
dom.mozApps.used: true
extensions.lastAppVersion: 38.0.5
gfx.direct3d.last_used_feature_level_idx: 0
media.gmp-eme-adobe.lastUpdate: 1433311748
media.gmp-eme-adobe.version: 10
media.gmp-gmpopenh264.lastUpdate: 1432043571
media.gmp-gmpopenh264.version: 1.4
media.gmp-manager.buildID: 20150525141253
media.gmp-manager.lastCheck: 1433921014
network.cookie.prefsMigrated: true
network.predictor.cleaned-up: true
places.database.lastMaintenance: 1433920538
places.history.expiration.transient_current_max_pages: 104858
plugin.disable_full_page_plugin_for_types: application/pdf
plugin.importedState: true
privacy.sanitize.migrateFx3Prefs: true
storage.vacuum.last.index: 1
storage.vacuum.last.places.sqlite: 1433834210

Preferenze importanti bloccate
------------------------------

JavaScript
----------

GC incrementale: true

Accessibilità
-------------

Attivato: false
Impedisci accessibilità: 0

Versioni librerie
-----------------

NSPR
Versione minima prevista: 4.10.8
Versione in uso: 4.10.8

NSS
Versione minima prevista: 3.18.1 Basic ECC
Versione in uso: 3.18.1 Basic ECC

NSSSMIME
Versione minima prevista: 3.18.1 Basic ECC
Versione in uso: 3.18.1 Basic ECC

NSSSSL
Versione minima prevista: 3.18.1 Basic ECC
Versione in uso: 3.18.1 Basic ECC

NSSUTIL
Versione minima prevista: 3.18.1
Versione in uso: 3.18.1

Caratteristiche sperimentali
----------------------------

Comment 7

4 years ago
Milan, can you/someone finish off triaging this to the right gfx folks? :-)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(milan)
Whiteboard: gfx-noted
If you disable layers acceleration, does the crash still happen? You can disable layers acceleration with:

1) go to about:config
2) Set the preference "layers.acceleration.disabled" to true
3) Restart firefox
4) Try loading the URL again

Does it still crash?
Flags: needinfo?(devotip)
It's in line, and it's either part of the group that deals with driver reset crashes, or it may take a while for us to get to it as it currently has 10 crashes in the past week; our current priority bug has 14000 :)

Bas, at least one of these has the same D2D+/D2D- and D3D11+/D3D11- issues (e.g., https://crash-stats.mozilla.com/report/index/35af96e1-96d9-4892-9363-a99442150606)

For this to happen, gfxWindowsPlatform::VerifyD2DDevice gets called twice from gfxWindowsPlatform::UpdateRenderMode.

The first call should be from gfxWindowsPlatform constructor, the subsequent one could happen from nsWindow::GetLayerManager (if we lost mLayerManager).

More likely it is the call in nsWindow::OnPaint that we make if DidRenderingDeviceReset returns true.
Flags: needinfo?(milan)
(In reply to Milan Sreckovic [:milan] from comment #9)
> It's in line, and it's either part of the group that deals with driver reset
> crashes, or it may take a while for us to get to it as it currently has 10
> crashes in the past week; our current priority bug has 14000 :)
> 
> Bas, at least one of these has the same D2D+/D2D- and D3D11+/D3D11- issues
> (e.g.,
> https://crash-stats.mozilla.com/report/index/35af96e1-96d9-4892-9363-
> a99442150606)
> 
> For this to happen, gfxWindowsPlatform::VerifyD2DDevice gets called twice
> from gfxWindowsPlatform::UpdateRenderMode.
> 
> The first call should be from gfxWindowsPlatform constructor, the subsequent
> one could happen from nsWindow::GetLayerManager (if we lost mLayerManager).
> 
> More likely it is the call in nsWindow::OnPaint that we make if
> DidRenderingDeviceReset returns true.

Note a subtle difference, these get + first, - next, that can simply happen if for some reason we lose the device, indeed check the rendering device is reset, and then attempt to reinitialize.

The other ones get - first, and then +, the thing is, if we got - on D3D11 Layers in the first place, DidDeviceReset should never return true and we should never try again.. Unless something is not working as intended.
Flags: needinfo?(bas)
For the record, these reports contain both 0x887a0005 (device removed errors), and so are likely some form of TDR crash, and 0x88990015 (wrong resource domain, this -can- be expected and -should- be dealt with, but maybe somewhere we're still confusing the intel driver), but the crash you pointed at definitely seems to be in the TDR bucket.
Crash Signature: igd10iumd32.dll@0x2a3a2 → [@ igd10iumd32.dll@0x2a3a2]
Closing this bug as there have been no reports since July. Please reopen this bug report if you can reproduce the crash in a current Firefox version.
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.