1708417 - Rendering glitches with canvas when using openseadragon

Status: UNCONFIRMED

(Core :: Graphics: Canvas2D, defect)

Description

[j.hudecek]

Attachment: error canvas.jpg

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

Steps to reproduce:

Open https://openseadragon.github.io scroll down to the image and zoom in (using the scroll wheel). OpenSeaDragon uses canvas.drawImage in requestAnimationFrame, see the sources.
This happens everytime we refresh the page on some 32-bit and some 64bit Firefox 88 running on Windows 7 x64 with integrated Intel GPU in i5-3470S

Actual results:

next to the zoomed in image there are lines of the non-zoomed image and black lines

Expected results:

image is zoomed in

Comment 1

[BugBot [:suhaib / :marco]]

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Timothy Nikkel (:tnikkel)]

Is this a regression?

Comment 3

[j.hudecek]

Yes, version 83 works so it broke somewhere in between. We noticed it in a software we use everyday so we would have noticed it if it was a problem earlier, so it's likely that it's caused by the 88

Comment 4

[Timothy Nikkel (:tnikkel)]

Can you use https://mozilla.github.io/mozregression/ to narrow down what caused it? (I don't see this on my machine, or I would do it myself)

Comment 5

[Dzmitry Malyshau [:kvark]]

Strange. I tested it on latest Nightly with Linux/Nvidia and macOS/Intel, and I see no issues like this.

Comment 6

[j.hudecek]

Sorry, we couldn't get it to run the corporate machines, the antivirus would always kick in (even firefox flags it as "virus or malware"!?)

Comment 7

[BugBot [:suhaib / :marco]]

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit auto_nag documentation.

Comment 8

[Timothy Nikkel (:tnikkel)]

There was a time when mozregression would get wrongly flagged by antivirus, but I think that is fixed now. I can't reproduce the problems either unfortunately.