crash in mozilla::gl::SharedSurface_ANGLEShareHandle::ProducerAcquireImpl

NEW
Unassigned

Status

()

Core
Canvas: WebGL
P3
critical
2 years ago
7 months ago

People

(Reporter: milan, Unassigned)

Tracking

({crash})

unspecified
Unspecified
Windows NT
crash
Points:
---

Firefox Tracking Flags

(firefox47 affected, firefox48 affected)

Details

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

(Reporter)

Description

2 years ago
This bug was filed from the Socorro interface and is 
report bp-3ce9a478-f6af-48f8-8a49-37d8c2160414.
=============================================================

The other place where we timeout for the sync, we gfxDevCrash instead.  Should we change that in here as well?
(Reporter)

Comment 1

2 years ago
(In reply to Milan Sreckovic [:milan] from comment #0)
> The other place where we timeout for the sync, we gfxDevCrash instead. 
> Should we change that in here as well?

"instead" of MOZ_CRASH, that is.
Whiteboard: [gfx-noted]
Crash volume for signature 'mozilla::gl::SharedSurface_ANGLEShareHandle::ProducerAcquireImpl':
 - nightly (version 50): 0 crash from 2016-06-06.
 - aurora  (version 49): 0 crash from 2016-06-07.
 - beta    (version 48): 9 crashes from 2016-06-06.
 - release (version 47): 27 crashes from 2016-05-31.
 - esr     (version 45): 0 crash from 2016-04-07.

Crash volume on the last weeks:
             Week N-1   Week N-2   Week N-3   Week N-4   Week N-5   Week N-6   Week N-7
 - nightly          0          0          0          0          0          0          0
 - aurora           0          0          0          0          0          0          0
 - beta             1          3          0          0          2          3          0
 - release          5          6          4          3          2          3          2
 - esr              0          0          0          0          0          0          0

Affected platform: Windows
status-firefox47: --- → affected
status-firefox48: --- → affected
(Reporter)

Updated

7 months ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.