Closed
Bug 1427112
Opened 6 years ago
Closed 6 years ago
Crash in mozilla::gl::GLContext::MakeCurrent const
Categories
(Core :: Graphics: CanvasWebGL, defect, P1)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox-esr52 | --- | unaffected |
firefox57 | --- | unaffected |
firefox58 | --- | unaffected |
firefox59 | --- | fix-optional |
firefox60 | --- | affected |
People
(Reporter: philipp, Assigned: jgilbert)
Details
(Keywords: crash, regression, Whiteboard: [gfx-noted])
Crash Data
This bug was filed from the Socorro interface and is report bp-af962f0f-db5b-4009-901f-6f8750171225. ============================================================= Top 10 frames of crashing thread: 0 XUL mozilla::gl::GLContext::MakeCurrent const gfx/gl/GLContext.cpp:3047 1 XUL mozilla::layers::CompositingRenderTargetOGL::~CompositingRenderTargetOGL gfx/layers/opengl/CompositingRenderTargetOGL.cpp:21 2 XUL mozilla::layers::CompositingRenderTargetOGL::~CompositingRenderTargetOGL gfx/layers/opengl/CompositingRenderTargetOGL.cpp:20 3 XUL mozilla::layers::ContainerLayerComposite::~ContainerLayerComposite mfbt/RefCounted.h:208 4 XUL <name omitted> gfx/layers/composite/ContainerLayerComposite.cpp:661 5 XUL mozilla::layers::ContainerLayer::RemoveChild gfx/layers/Layers.h:821 6 XUL mozilla::layers::ContainerLayerComposite::~ContainerLayerComposite gfx/layers/composite/ContainerLayerComposite.cpp:674 7 XUL <name omitted> gfx/layers/composite/ContainerLayerComposite.cpp:661 8 XUL mozilla::layers::LayerTransactionParent::~LayerTransactionParent gfx/layers/Layers.h:821 9 XUL non-virtual thunk to mozilla::layers::LayerTransactionParent::~LayerTransactionParent gfx/layers/ipc/LayerTransactionParent.cpp:66 ============================================================= crashes with this signature are newly showing up on macos in firefox 59.
Comment 1•6 years ago
|
||
Hi :philipp, I enter the link of bp-af962f0f-db5b-4009-901f-6f8750171225, but it shows nothing. Could you help me confirm if it does still have. Thanks!
Flags: needinfo?(madperson)
Reporter | ||
Comment 2•6 years ago
|
||
unfortunately all existing crash reports were purged in bug 1427111 and there were no new reports in the past couple of days. (keeping the ni in place to be reminded to look again for new reports in a couple of days time).
Reporter | ||
Comment 3•6 years ago
|
||
first new report about this that got submitted was bp-31076a7d-f643-40ed-b5b3-d910c0171230
Flags: needinfo?(madperson)
Comment 4•6 years ago
|
||
Hi Jeff, It looks like a regression from Bug 1390386. Can you take a look at this?
Flags: needinfo?(jgilbert)
Updated•6 years ago
|
Assignee: nobody → jgilbert
Priority: -- → P1
Updated•6 years ago
|
Whiteboard: [gfx-noted]
Comment 5•6 years ago
|
||
Marking 60 as affected and fix optional per triage team.
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(jgilbert)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•