Arch Linux
GNOME Shell 3.28.2 on Wayland

The capture attached is a Youtube video but it fails in all webpages.

decedion@ Thanks for the issue.

Tested this issue on Ubuntu 14.04 on GNOME Flashback(Compiz) environment on the reported version 67.0.3396.87 by following the below steps.

1. Launched Chrome and navigated to few webpages like google and Youtube.
2. Hit the F11 button, and when in Full screen, cannot observe any artifacts on the page.
Attached is the screen cast for reference.

Request you to retry the issue on new chrome profile without any flags/extensions and update the thread with the observations.

Thanks..

Deleted: 855040.ogv 23.3 MB

855040.ogv 23.3 MB Download

I have tested it on a guest session of Chromium (no extensions and default flags) and same problem. I attach screencast.
When I exit from full-screen, the browser still shows artifacts. I have to restart it.

Deleted: screencast-chromium.webm 7.7 MB

	screencast-chromium.webm 7.7 MB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

decedion@ Thanks for the update.

Tested this issue on Ubuntu 17.10 on the reported version 67.0.3396.87 and unable to reproduce the issue.

On navigating to chrome://flags page and any other web page, and hitting F11 key for full screen, cannot observe any artifacts on the page.
Attached is the chrome://gpu details for reference.

As this issue is not reproduced at TE end, removing 'Needs-Bisect' label.
Requesting Internals>GPU team to look into the issue and help in further triaging.

Thanks..

Deleted: gpu (1).html 64.7 KB

gpu (1).html 64.7 KB View Download

Are you tested on Gnome Shell on Wayland?

The issue seems to be reproducible on Gnome Shell on Wayland. The test team doesn't have that specific Gnome Shell on Wayland environment to test the issue. Hence, adding label TE-Hardware-Dependency.

Thanks...!!

I've tested it with Gnome Shell on Xorg and it works well. The problem is with Wayland.

rjkroege@ would know more about Wayland.

Is this running Chrome Wayland? Or Chrome X11 via X11 adapter on Wayland?

Is there a Chrome Wayland!? Where can I download it?

This bug appears when Chromium/Chrome stable version runs on Wayland. I think the stable version is always (for now) for X11, no?

The current stable version of Chrome Linux is X11 only. Chromium wayland is still wip.

Please confirm: this bug happens iff Chrome stable is running on X11-emulation-Wayland? If so, this would appear to be a bug with the X11-emulation system.

I repeat: "This bug appears when Chromium/Chrome stable version runs on Wayland."

maksim.sisov@ any ideas here? Why the X11 emulation on Wayland would do this?

Another data point:

This issue only occurs for me on the secondary monitor (confirmed through switching primary/secondary settings), and only when the window is already fully maximized. Entering full screen while the window is not maximized will not trigger the issue. Resizing the window after artifacts show up eliminates said artifacts and resolves all visible issues.

I have attached the `version` and `gpu` pages for stable and unstable builds, which both exhibit this bug. The stable files were using `--use-gl=osmesa`. The `--disable-gpu-driver-bug-workarounds`, `--use-gl=osmesa`, and `--ignore-gpu-blacklist` flags do not have any affect on this issue. I run Arch Linux w/ Gnome on Wayland (fully patched as of time of this post).

Deleted: stable-version.html 4.2 KB

stable-version.html 4.2 KB View Download

Deleted: stable-gpu.html 88.0 KB

stable-gpu.html 88.0 KB View Download

Deleted: dev-version.html 5.1 KB

dev-version.html 5.1 KB View Download

Deleted: dev-gpu.html 71.4 KB

dev-gpu.html 71.4 KB View Download