1656774 - Canvas2D renders entirely black in some cases

Status: RESOLVED DUPLICATE of bug 1654477

(Core :: Graphics, defect, P3)

Description

[Pomax]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0

Steps to reproduce:

Running Firefox Nightly 81.0a1 (2020-08-02) x64 on Windows 10 Pro x64 with an Nvidia GTX 970, I am seeing Canvas2D graphic refreshing that leaves the canvas entirely black. During event looping (e.g. redraws due to mousemove) this leads to a visible graphic turn into horrible black flickering, and ending in a black graphic once the events stop.

An example URL for which this happens is https://pomax.github.io/bezierinfo/#yforx, with the "Finding t, given x=x(t). Left: our curve, right: the x=x(t) function" figure consistently showing this rendering bug.

Comment 1

[Pomax]

Attachment: 01-initial-load.jpg

Comment 2

[Pomax]

Attachment: 02-mousemove-result.jpg

Comment 3

[Alice0775 White]

I can reproduce the issue(black(sometimes white) flickering) on Nightly81.0a1 windows10 when with/without WebRender.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=df4d3efbfa453cf1e0da54a44df349e130731f74&tochange=a22ce6ad4e273a47c9f4481e2462efa35b17d8eb

Comment 4

[Bob Owen (:bobowen)]

Thanks for reporting this.

It looks like this might be similar to bug 1654477.
I have a potential fix for that, although there might be complications.
I'll test with that fix when I get a chance.

Comment 5

[Pomax]

Cheers!

Comment 6

[Bob Owen (:bobowen)]

This does appear to be fixed, by my potential fix for bug 1654477.
I'm not going to duplicate this over just yet, because the STR for that bug still shows some issues.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:ktaeleman, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 9

[Jim Mathies [:jimm]]

This blocks the rollout bug for remote Canvas.

Comment 10

[Bob Owen (:bobowen)]

I'm pretty confident this was a duplicate of bug 1654477.
When I came to retest I could not reproduce even without that fix, so I can't be totally sure.
If anyone can still reproduce please re-open.