Closed
Bug 1662836
Opened 4 years ago
Closed 4 years ago
Use detailed error message for failure ID for WebRender initialization failures
Categories
(Core :: Graphics: WebRender, task)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
82 Branch
| Tracking | Status | |
|---|---|---|
| firefox82 | --- | fixed |
People
(Reporter: aosmond, Assigned: aosmond)
Details
Attachments
(1 file)
WebRender can fail to initialization for many reasons. This isn't useful for diagnosing it. Let's expose the detailed error message we get from WR as the failure reason.
|
Assignee | |
Comment 1•4 years ago
|
||
We don't know why we see initialization failures in the telemetry which
makes it hard to investigate why users aren't getting WebRender and
instead fallback to basic. Let's expose the detailed error message
WebRender already generates and puts in the critical log.
Pushed by aosmond@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fe5a38698226 Expose detailed initialization failure reason for WebRender. r=kvark
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•