All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
Date: Fri, 01 May 2015 03:55:37 +0000	[thread overview]
Message-ID: <bug-90264-502-XL28ihvas1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90264-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1202 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=90264

--- Comment #4 from falaca@gmail.com ---
When I set LIBGL_ALWAYS_SOFTWARE=1, chrome://gpu shows "Software only" for all
the features, and the GL_RENDERER string is "Gallium 0.4 on llvmpipe (LLVM 3.6,
128 bits)".

It does appear to be a bug somewhere in the Radeon-specific code, but based on
my tests above, it looks like the bug is triggered by the Mesa commit that I
bisected. The purpose of the commit (if I understand correctly) is to avoid
processing redundant viewport updates, so it seems like that causes the radeon
driver to display stale content.

This may or may not be related, but here is another interesting screenshot:
https://www.dropbox.com/s/9ydljofmj8kfxme/corruption_2.png?dl=0

That is my desktop, and you can see some white tiles surrounding the "Portal"
icon. Those tiles are showing content from another window (Android Studio)
which I had previously launched and then minimized. If you download the picture
and zoom in, you can see the little folder icons with the Android logo on them.
So that also seems like an issue of displaying stale content.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2053 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-05-01  3:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01  3:08 [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome bugzilla-daemon
2015-05-01  3:12 ` bugzilla-daemon
2015-05-01  3:26 ` bugzilla-daemon
2015-05-01  3:37 ` bugzilla-daemon
2015-05-01  3:55 ` bugzilla-daemon [this message]
2015-05-01  4:01 ` bugzilla-daemon
2015-05-01 19:08 ` bugzilla-daemon
2015-05-01 22:16 ` bugzilla-daemon
2015-05-25 18:45 ` bugzilla-daemon
2015-06-10 12:34 ` bugzilla-daemon
2015-06-10 12:58 ` bugzilla-daemon
2015-06-10 17:33 ` bugzilla-daemon
2015-06-10 17:37 ` bugzilla-daemon
2015-06-10 19:09 ` bugzilla-daemon
2015-06-10 19:44 ` bugzilla-daemon
2015-06-10 19:57 ` bugzilla-daemon
2015-06-10 20:58 ` bugzilla-daemon
2015-06-10 21:12 ` bugzilla-daemon
2015-06-10 21:36 ` bugzilla-daemon
2015-06-10 23:34 ` 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-90264-502-XL28ihvas1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.