Open
Bug 1554719
Opened 5 years ago
Updated 6 months ago
Capture GL driver messages on panics
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Tracking
()
NEW
People
(Reporter: kvark, Unassigned)
References
(Blocks 1 open bug)
Details
Current error propagation in WR assumes that no panic occurs: errors are accumulated in a vector and then returned from render()
routine. WR bindings take that and issue the gfx critical error callback on each. This approach doesn't work when the driver panics, and we end up with no useful information to investigate.
Rough plan to solve this:
- Expose the error callback to WR, use internally instead of collecting errors in a vector
- Hook up
glDebugMessageCallback
with Error+ severity to this callback
This can be trivially tested by changing WR's GL operation to do something wrong and follow by a panic.
Updated•5 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•