Closed Bug 1379120 Opened 8 years ago Closed 8 years ago

Crash in mozilla::layers::SourceSurfaceImage::GetTextureClient

Categories

(Core :: Graphics: WebRender, defect)

Product:
Core
Component:
Graphics: WebRender
Version:
56 Branch
Platform:
Unspecified
Windows 10
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox54 --- unaffected
firefox55 --- unaffected
firefox56 --- unaffected
firefox57 --- unaffected

People

(Reporter: calixte, Assigned: mtseng)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression, Whiteboard: [clouseau][gfx-noted])

Crash Data

This bug was filed from the Socorro interface and is report bp-ec45341c-bf24-4127-9d98-a55410170706. ============================================================= There is 1 crash in nightly 56 with buildid 20170706030206. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1376855. [1] https://hg.mozilla.org/mozilla-central/rev?node=47c66f214de35be5b863c1431abdd467794ef44e
Flags: needinfo?(mtseng)
Whiteboard: [clouseau] → [clouseau][gfx-noted]
Sorry for late reply, I'll keep tracking this bug. Thanks for report.
Flags: needinfo?(mtseng)
WebRender is non on by default.
Assignee: nobody → mtseng
status-firefox56: affected → unaffected
Status: NEW → ASSIGNED
Priority: P3 → P1
Whiteboard: [clouseau][gfx-noted] → [wr-mvp] [clouseau][gfx-noted]
Target Milestone: --- → mozilla57
There's a bunch of these crashes without WR enabled, on 52 ESR branch. There's only 4 with WR enabled, on 56/57. The most recent is at https://crash-stats.mozilla.com/report/index/e20ed0a1-3ad8-4482-ab67-014310170806, buildid 20170805100334 which is a month and a half ago. I think it's safe to close; we can reopen if it shows up again.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Priority: P1 → --
Whiteboard: [wr-mvp] [clouseau][gfx-noted] → [clouseau][gfx-noted]
Target Milestone: mozilla57 → ---
You need to log in before you can comment on or make changes to this bug.