Bug 105243 - vsync(?) artifact
Summary: vsync(?) artifact
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: 17.2
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: mesa-dev
QA Contact: mesa-dev
Depends on:
Reported: 2018-02-25 18:30 UTC by Frank
Modified: 2019-09-18 20:18 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Example 1 (1.30 MB, image/png)
2018-02-25 18:30 UTC, Frank
Example 2 (635.11 KB, image/png)
2018-02-25 18:30 UTC, Frank

Description Frank 2018-02-25 18:30:09 UTC
Created attachment 137594 [details]
Example 1

Hi all! Since about two years (estimated) I really often encounter an artifact which seems like a vsync issue – that is a border due to displaying two frames partly at the same time. This border goes across my screen and always has the same position (a year ago it was more like an upside-down parable, but now it’s a line). I add two screen-shots so you see how it looks. It occurs both in videos, when the camera is moving slowly, and also sometimes if I scroll through text. It is not persistent, but about appears every some seconds.

Video-wise, some sources (like Netflix in Firefox) run smooth, if I recall this correctly – but as far as I remember, all videos I play with Totem/Gnome-MPV/VLC are exposed to that issue – which is also true for watching SkyGo via Firefox (in contrast to Netflix).

I don’t really know where I should file this bug report, so I’ll try here on Mesa, as this happens on both an Intel, as on an AMD system:

Dell XPS 15 9550
• Intel® HD Graphics 530 (Skylake GT2) / NV117 (gnome-control-center output)
• Nouveau for the NVidia card (but I don’t use that card explicitly, so it shouldn’t be used at all, I assume)
• Fedora 24-27
• Wayland
• Mesa 17.2 (but as I said, this occurs since about two years)

• AMD® A8-7600 radeon r7, 10 compute cores 4c+6g x 4
• Tested with Debian Stretch, Debian Testing & Fedora 27
• Wayland
Comment 1 Frank 2018-02-25 18:30:40 UTC
Created attachment 137595 [details]
Example 2
Comment 2 GitLab Migration User 2019-09-18 20:18:17 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/921.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.