Open Bug 1928289 Opened 2 days ago Updated 2 days ago

MozAfterPaint might not be fired if the GPU process crashes at the right time

Categories

(Core :: Graphics, defect, P3)

defect

Tracking

()

People

(Reporter: botond, Unassigned)

References

(Blocks 1 open bug)

Details

In bug 1925896, Brad ran into a scenario where nsIDOMWindowUtils.isMozAfterPaintPending can be true, but a "MozAfterPaint" event never actually arrives if the GPU process crashes at the right time.

The patch for bug 1925896 works around this in one place where isMozAfterPaintPending is used, but the underlying issue could potentially cause other msbehaviour.

From this review comment:

Note that this test failure makes me suspect there a race condition where a content process has sent a transaction but the GPU process hasn't yet process it, then if the GPU process is crashed, the transition will be lost. A worst case is that blank page persists until a flush happens on the content.

Blocking this on the meta gpu-process should ensure I get to it eventually.

Blocks: gpu-process
Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.