From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109235] Using named pixmap of window right after resizing results in garbage content
Date: Sun, 06 Jan 2019 21:00:31 +0000 [thread overview]
Message-ID: <bug-109235-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1082 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109235
Bug ID: 109235
Summary: Using named pixmap of window right after resizing
results in garbage content
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: yshuiv7@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
compton is a glx based compositor, when a window is resized, compton release
the previously bound pixmap, and create a new named pixmap and bind that to a
texture, and then render the screen with that.
With the amdgpu/radeonsi driver, that sometimes result in garbage content.
You can find more details, screenshot, and recordings here [1]
[1]: https://github.com/yshui/compton/issues/85
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2519 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-01-06 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 21:00 bugzilla-daemon [this message]
2019-01-06 21:18 ` [Bug 109235] Using named pixmap of window right after resizing results in garbage content bugzilla-daemon
2019-01-09 16:54 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-109235-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox