crash in mozilla::layers::TextureChild::Release

NEW
Unassigned

Status

()

Core
Graphics
P3
critical
2 years ago
3 months ago

People

(Reporter: adalucinet, Unassigned)

Tracking

({crash})

41 Branch
All
Windows
crash
Points:
---

Firefox Tracking Flags

(firefox42 wontfix, firefox43 wontfix, firefox44 wontfix, firefox45 affected, firefox46 unaffected, firefox48 affected, firefox-esr45 affected)

Details

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

(Reporter)

Description

2 years ago
This bug was filed from the Socorro interface and is 
report bp-3ef9422c-25da-4fb0-8191-926722160122.
=============================================================
Affected builds:
* 42.0 build 2
* 44 beta 9
* 44.0RC, both builds 1 & 2

Unaffected builds:
* 43.0.4 build 3
* latest Aurora 45.0a2
* latest Nightly 46.0a1

Affected OS: Windows

Steps to reproduce: same as in bug 1241484 comment 0

Additional notes: 
1. A weird thing here is the fact that with 42.0 build 2 and 44 beta 9 I am able to reproduce over and over again with the same profile, and with 44.0RC (both builds) only once per profile.
2. More reports: https://crash-stats.mozilla.com/report/list?product=Firefox&range_unit=days&range_value=7&signature=mozilla%3A%3Alayers%3A%3ATextureChild%3A%3ARelease
Looking at 6-months of crash data this goes back to at least Firefox 41.0b1. It's strange that we only see reports on Beta and Release, not Aurora or Nightly. There are no strong correlations to specific hardware.

Alexandra, can you please provide a copy of about:support and see if you can regress this on Nightly?
Keywords: regressionwindow-wanted
Whiteboard: [gfx-noted]
Version: 44 Branch → 41 Branch
status-firefox42: --- → affected
status-firefox43: --- → unaffected
status-firefox44: --- → affected
status-firefox45: --- → unaffected
status-firefox46: --- → unaffected
(Reporter)

Comment 2

2 years ago
No crash encountered with 40 beta 9 nor 40.0.3, but 41 beta 1 is indeed crashing: bp-a9a57d2e-009f-4795-a7ec-d19472160126.

After further manual investigations:
Last good Nightly: 2015-06-05
First bad Nightly: 2015-06-06 → bp-06c89842-08e6-4a37-b82e-9d9fd2160126

Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2015-06-05&enddate=2015-06-06

about:support details:
Graphics
Adapter Description	ATI Radeon 3000 Graphics
Adapter Drivers	aticfx64 aticfx64 aticfx32 aticfx32 atiumd64 atidxx64 atiumdag atidxx32 atiumdva atiumd6a atitmm64
Adapter RAM	512
Asynchronous Pan/Zoom	wheel input enabled
ClearType Parameters	D [ Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 50 ] D [ Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 50 ]
Device ID	0x9616
Direct2D Enabled	true
DirectWrite Enabled	true (6.2.9200.17568)
Driver Date	4-29-2013
Driver Version	8.970.100.1100
GPU #2 Active	false
GPU Accelerated Windows	1/1 Direct3D 11 (OMTC)
Subsys ID	00000000
Supports Hardware H264 Decoding	No; Failed to find an appropriate decoder GUID
Vendor ID	0x1002
WebGL Renderer	Google Inc. -- ANGLE (ATI Radeon 3000 Graphics Direct3D11 vs_4_0 ps_4_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0
(In reply to Alexandra Lucinet, QA Mentor [:adalucinet] from comment #2)
> Pushlog:
> http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2015-06-
> 05&enddate=2015-06-06

Please refrain from using dates in pushlogs and instead provide changeset IDs from about:buildconfig. In this case, the correct pushlog is https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0496b5b3e9ef&tochange=4a07e1ac3cdf

> Driver Date	4-29-2013
> Driver Version	8.970.100.1100

Please update your graphics drivers.
(Reporter)

Comment 4

2 years ago
(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #3)
> > Driver Date	4-29-2013
> > Driver Version	8.970.100.1100
> 
> Please update your graphics drivers.

Based on AMD’s website - http://support.amd.com/en-us/download/desktop/legacy?product=legacy2&os=Windows%207%20-%2064, AMD HD3000 does not have a newer version of driver; I am running the latest. Windows also prompts that the driver software for my device is up to date.
Does disabling hardware acceleration work around this issue?
(Reporter)

Comment 6

2 years ago
(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #5)
> Does disabling hardware acceleration work around this issue?

No, it's the same: bp-f2614eba-96aa-443c-a9d4-4ac842160129
Can you verify if this reproduces in Nightly with e10s on and off?
status-firefox42: affected → wontfix
status-firefox43: unaffected → affected
(Reporter)

Comment 8

2 years ago
(In reply to Anthony Hughes, QA Mentor (:ashughes) from comment #7)
> Can you verify if this reproduces in Nightly with e10s on and off?

Still unable to reproduce *this* signature on Nightly builds - tested with 47.0a1 (from 2015-01-31), e10s enabled and disabled. 
Only encountered bug 1241876 - bp-241621f0-48c5-41e1-b0ca-9c0392160201 - with e10s disabled.
This is no longer reproducible on the latest Nightly(47.0a1) but is reproducible on the latest release (44.0.2).

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160221030340

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20160210153822

Based on comment 2, I will remove the "regressionwindow-wanted" keyword.
Keywords: regressionwindow-wanted
Could you please check Firefox 45? If this doesn't affect the current release it can be closed.
status-firefox43: affected → wontfix
status-firefox44: affected → wontfix
(Reporter)

Comment 11

2 years ago
(In reply to Anthony Hughes (:ashughes) [GFX][QA][Mentor] from comment #10)
> Could you please check Firefox 45? If this doesn't affect the current
> release it can be closed.

I could not reproduce this signature with 45.0RC build 2 (Build ID: 20160303134406), under Windows 7 64-bit; only encountered [@ mozilla::layers::TextureChild::WaitForCompositorRecycle | mozilla::layers::CanvasClientSharedSurface::Updated ] [1], which is bug 1241484 (already fixed on 47).

[1]
bp-81ace74a-e12e-4cdc-8bc4-f96b82160310
bp-3a925664-0023-482c-855d-ad6262160310
bp-4e5066bb-2e1f-4309-a7f0-a972b2160310
We have some crashes with 45.0 in Release, bp-2ee15dad-0cf7-49ca-9e3d-021642160414 for example. As of yet I don't see any crashes with 46 or later. Keeping this open for now but this will likely get closed in the future if volume remains low.
status-firefox45: unaffected → affected
Crash volume for signature 'mozilla::layers::TextureChild::Release':
 - nightly (version 50): 0 crashes from 2016-06-06.
 - aurora  (version 49): 0 crashes from 2016-06-07.
 - beta    (version 48): 1 crash from 2016-06-06.
 - release (version 47): 82 crashes from 2016-05-31.
 - esr     (version 45): 61 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       0       0       0       0
 - aurora        0       0       0       0       0       0       0
 - beta          0       1       0       0       0       0       0
 - release      10      12      11      12       4       9      18
 - esr           7       5       4       9       8       7       6

Affected platform: Windows
status-firefox48: --- → affected
status-firefox-esr45: --- → affected
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.