1653283 - Contents bleeding from one tab into another

Status: RESOLVED FIXED

(Core :: Graphics: WebRender, defect)

Description

[Dave Townsend [:mossop]]

Attachment: Screenshot

On today's nightly (20200716094032) on macOS 10.15.5 on a 2018 MBP I am seeing content from one tab bleeding into other tabs. It is fairly random but seems to only happen with webrender enabled. The source tab is not necessarily from the same process and as you can see from the top-left of the screenshot it also affects areas outside the content area.

Once a tab has bad content switching away and back to it usually still shows bad content in the same areas. Sometimes that content is just all black, sometimes it is from a different tab (but not necessarily in the same position of the content). Switching away and back sometimes changes the exact content of the bad area. Scrolling the tab shows the bad content scrolling too!

Comment 1

[Jessie [:jbonisteel] pls NI]

Possibly related to bug 1640960 - we have requested a backout again

Comment 2

[Dave Townsend [:mossop]]

Often, opening the find bar on a tab that is rendering fine will suddenly cause new content to appear from a different tab.

Comment 3

[David Burns :automatedtester]

I'm seeing the same bleed through as mossop for what it's worth

Comment 4

[Caspy7]

Attachment: Render Issue

I do not know with certainty that this is the same issue, but I'm on Nightly build 80.0a1 (2020-07-16) (64-bit) for Windows and I use an extension called Imagus that let's me hover over links and images to preview the linked image or video. Today I noticed that rectangular artifacts from the preview images are not disappearing immediately afterwards (sometimes quicker, sometimes slower).

I was pointed in this direction so thought I'd attach a screencast in case it's a helpful data point.

Comment 5

[Glenn Watson [:gw]]

If anyone is able to reliably reproduce this, would it be possible to get a mozregression range?

Comment 6

[Jessie [:jbonisteel] pls NI]

Do you see this still in the latest Nightly (with WebRender enabled of course)?

Comment 7

[Dave Townsend [:mossop]]

Yes this seems fixed in today's nightly.

Comment 8

[Jessie [:jbonisteel] pls NI]

Caspy7, if you still see the issue you described in the latest Nightly, can you file a separate bug? Seems like it would be a different issue, if it still exists.

Comment 9

[Caspy7]

(In reply to Jessie [:jbonisteel] pls NI from comment #8)

Caspy7, if you still see the issue you described in the latest Nightly, can you file a separate bug? Seems like it would be a different issue, if it still exists.

The issue does seem resolved in today's build.

Comment 10

[David Burns :automatedtester]

Not seen it for a few days now so guessing the backout worked

Comment 11

[Daniel Bodea [:danibodea]]

I am removing the regressionwindow-wanted tag since the issue appears to have been fixed.
Please put it back it it still needs investigation. Thanks.

Comment 12

[Darkspirit]

Bug 1653413 fixed DirectComposition for Win10.
As this occurred on macOS and seems to be fixed, the backout of bug 1640960 might have fixed it.

Comment 13

[Darkspirit]

By bug 1640960 comment 17.

Comment 14

[Darkspirit]

Fixed by backout: bug 1640960 comment 24