Closed
Bug 1297390
Opened 8 years ago
Closed 6 years ago
Crash in mozilla::layers::CompositingRenderTargetOGL::~CompositingRenderTargetOGL
Categories
(Core :: Graphics: Layers, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: standard8, Assigned: nical)
References
Details
(Keywords: crash, Whiteboard: [gfx-noted])
Crash Data
+++ This bug was initially created as a clone of Bug #1280110 +++ I've been seeing this today very frequently when running activity stream tests on latest nightly - its happened around 50% of the time, it crashes when being shutdown at the end of the test run. bp-bc585883-65f5-4ffd-a4d0-d47be2160823 bp-127381ea-e69d-4011-8af1-29de22160823 bp-c4243f9d-d016-4361-9a0a-bb9a22160823 bp-2ad8e178-d2a6-43dc-9060-6d7622160823
Andrew, I know this is on OS X, but could it be a fallout from the Linux OGL patches?
Flags: needinfo?(andrew)
Comment 2•8 years ago
|
||
It's not very likely, the OGL compositor changes made recently have been confined to GLContextProviderGLX and gfxPlatformGtk. I don't think any of them should affect render target teardown on OS X.
Flags: needinfo?(andrew)
Updated•8 years ago
|
Assignee: nobody → nical.bugzilla
Comment 3•8 years ago
|
||
Crash volume for signature 'mozilla::layers::CompositingRenderTargetOGL::~CompositingRenderTargetOGL': - nightly (version 51): 7 crashes from 2016-08-01. - aurora (version 50): 1 crash from 2016-08-01. - beta (version 49): 0 crashes from 2016-08-02. - release (version 48): 42 crashes from 2016-07-25. - esr (version 45): 0 crashes from 2016-05-02. Crash volume on the last weeks (Week N is from 08-22 to 08-28): W. N-1 W. N-2 W. N-3 - nightly 0 0 1 - aurora 1 0 0 - beta 0 0 0 - release 13 4 0 - esr 0 0 0 Affected platform: Mac OS X Crash rank on the last 7 days: Browser Content Plugin - nightly #135 - aurora #1550 - beta - release #819 - esr
status-firefox48:
--- → affected
status-firefox50:
--- → affected
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Comment 4•6 years ago
|
||
Nothing in the last 6 months, except on builds older than 54.0.1. One crash on 61.0.1, but that was recorded as EXC_BAD_ACCESS / KERN_INVALID_ADDRESS rather than EXC_BAD_ACCESS / EXC_I386_GPFLT which makes me wonder if that was a different issue, e.g. an issue with the mac itself. Therefore going to mark this as WFM as this seems to have gone away.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•