Closed
Bug 1663923
Opened 4 years ago
Closed 4 years ago
Cover more cases where we need a reason 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)
References
Details
Attachments
(1 file)
We are seeing empty reasons for why the user failed to get WebRender during initialization. At a glance, this could happen because of several (theoretical) reasons:
- The sync call EnsureConnected failed due to a crash.
- The WebRenderBridgeParent was destroyed before EnsureConnected came through.
- Some bug which causes us to not set a reason otherwise.
This bug should add an explicit reason for all three so that we can confirm. I suspect it is 1).
|
Assignee | |
Comment 1•4 years ago
|
||
Pushed by aosmond@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/598cb04b94e4
Cover more WebRender initialization failure paths with explicit reasons. 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
•