Closed Bug 1195110 Opened 6 years ago Closed 6 years ago

crash in @0x0 | mozilla::layers::CompositingRenderTargetOGL::~CompositingRenderTargetOGL()

Categories

(Core :: Graphics: Layers, defect)

x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla43
Tracking Status
firefox42 --- affected
firefox43 --- fixed

People

(Reporter: johnp, Assigned: acomminos)

Details

(Keywords: crash)

Crash Data

Attachments

(1 file)

This bug was filed from the Socorro interface and is 
report bp-00e63b79-d80b-4130-9c91-1963b2150816.
=============================================================

Crash with latest Fedora 22 KDE using pretty much all experimental layers features (APZ, acceleration forced, use-image-offscreen-surfaces). No STR.

Happened two times already. Here's the previous report (August 1st):

bp-3555e5a8-bbff-45b4-aafe-d7b452150801
Looks like something bad is happening in the destructor. We should be able to figure out what by looking at the disassembly.
Flags: needinfo?(acomminos)
The only scenario I could find in the disassembly where we could jump to 0x0 would be if we're trying to call a symbol in a destroyed GLContext. The vtables of the participating classes seem sane.

We should modify the code here to check the result of GLContext::MakeCurrent before deleting the GL objects.
Flags: needinfo?(acomminos)
Attachment #8649487 - Flags: review?(jmuizelaar) → review+
Assignee: nobody → acomminos
Status: NEW → ASSIGNED
https://hg.mozilla.org/mozilla-central/rev/6f9182aaadb1
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
You need to log in before you can comment on or make changes to this bug.