Closed Bug 1350259 Opened 8 years ago Closed 8 years ago

Crash in @0x0 | mozilla::layers::TextureImageTextureSourceOGL::BindTexture

Categories

(Core :: Graphics: Layers, defect)

52 Branch
Unspecified
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox52 --- unaffected
firefox-esr52 --- unaffected
firefox53 --- unaffected
firefox54 --- unaffected
firefox55 --- fixed

People

(Reporter: calixte, Assigned: dvander)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression, Whiteboard: [clouseau])

Crash Data

Attachments

(1 file)

This bug was filed from the Socorro interface and is report bp-9d8f083c-20c3-433e-9262-385782170323. ============================================================= There are 2 crashes on nightly 55 with buildid 20170323110205. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1343814. [1] https://hg.mozilla.org/mozilla-central/rev?node=30cf9aea9a001b3a08e0d115a2dd1d865c718a72
Flags: needinfo?(dvander)
Assignee: nobody → dvander
Status: NEW → ASSIGNED
Flags: needinfo?(dvander)
I can reproduce this easily by dragging a tab from a window and dropping it onto another window.
Thanks, I can reproduce this with the STR in comment #1 and by forcing layers acceleration on.
Attached patch fixSplinter Review
Another think-o. If the compositor changes we have to deallocate device data.
Attachment #8851390 - Flags: review?(matt.woodrow)
Attachment #8851390 - Flags: review?(matt.woodrow) → review+
Pushed by danderson@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/ad9e2f221bbe Fix not deallocating device data after changing OGL compositors. (bug 1350259, r=mattwoodrow)
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: