Open
Bug 1357819
(wr-stability)
Opened 8 years ago
Updated 6 months ago
[meta] WebRender stability
Categories
(Core :: Graphics: WebRender, task, P5)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox56 | --- | unaffected |
firefox57 | --- | unaffected |
People
(Reporter: kats, Unassigned)
References
(Depends on 54 open bugs, Blocks 1 open bug)
Details
(Keywords: meta, Whiteboard: [gfx-noted])
Meta bug to track WR crashes and stability-related bugs. Right now I think this is an area of concern for WR because I'm not convinced we're getting reliable/useful information when WR crashes in the wild. I tried introducing crashes into the code locally and generally get results that I wouldn't expect (crashes in other parts of the code, or bogus stacks, or other such things).
I'm also unclear on which processes actually generate crash reports and what information is included in them. For example the WR?/WR+ annotation only shows up in the UI process crashes, and I don't think I have ever seen a WR crash report that claimed to be from the GPU process, although I have seen crash stacks in other processes for which the only explanation was a GPU process crash.
In all I feel like we need to spend some time investigating this situation and make sure the data and diagnostics we're getting are good.
One approach I've been taking (as time permits) is to do a windows try push with webrender force-enabled. This usually results in crashes left, right and center, and then takes some investigation to track down the root cause and how it propagates.
Reporter | ||
Updated•8 years ago
|
When testing webrender I frequently experience crashes when navigating back in the history via the context menu.
Reporter | ||
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Blocks: stage-wr-stages
Updated•7 years ago
|
status-firefox56:
--- → unaffected
status-firefox57:
--- → unaffected
Updated•4 years ago
|
Severity: normal → N/A
Type: enhancement → task
Priority: P3 → P5
Updated•8 months ago
|
Blocks: wr-projects
Updated•8 months ago
|
Depends on: wr-linux-stability
You need to log in
before you can comment on or make changes to this bug.
Description
•