Open Bug 1357819 (wr-stability) Opened 3 years ago Updated 9 days ago

[meta] WebRender stability


(Core :: Graphics: WebRender, enhancement, P3)

Other Branch



Tracking Status
firefox56 --- unaffected
firefox57 --- unaffected


(Reporter: kats, Unassigned)


(Depends on 22 open bugs, Blocks 1 open bug)


(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.
Alias: wr-stability
Depends on: 1354411
Depends on: 1343345
No longer depends on: 1354411
When testing webrender I frequently experience crashes when navigating back in the history via the context menu.
Depends on: 1379545
Depends on: 1390422
Depends on: 1390641
Depends on: 1391262
Depends on: 1391255
Depends on: 1392316
Depends on: 1391458
Depends on: 1393703
No longer depends on: 1393703
Depends on: 1394647
Depends on: 1397929
Depends on: 1399652
Depends on: 1405198
Depends on: 1408440
Depends on: 1408573
Depends on: 1409594
Depends on: 1416614
Depends on: 1417213
Depends on: 1440088
Depends on: 1448770
Depends on: 1470541
Depends on: 1478570
Depends on: 1479175
Depends on: 1485314
Depends on: 1494528
Depends on: 1502454
Depends on: 1500902
Depends on: 1504230
Depends on: 1508096
Depends on: 1546891
Depends on: 1550725
Depends on: 1558202
No longer depends on: 1560486
Depends on: 1582954
Depends on: 1583107
Depends on: 1583116
You need to log in before you can comment on or make changes to this bug.