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:08:54 +0000 [thread overview]
Message-ID: <bug-90264-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1693 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90264
Bug ID: 90264
Summary: [Regression, bisected] Tooltip corruption in Chrome
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: falaca@gmail.com
CC: kenneth@whitecape.org
There is intermittent tooltip corruption in Chrome, after the following Mesa
commit:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=95073a2dca03a48f4c77bc846a4a6d1f0eb81ae6
In order to verify, I built mesa 10.6 master from git (w/ llvm 3.4.2, to stay
consistent with my git bisect) with those lines commented, and the bug is no
longer present.
The bug has been reported here, and affects both r600 and radeonsi users:
https://code.google.com/p/chromium/issues/detail?id=442111
On that page, affected users are reporting a range of kernel versions (3.16+)
and mesa versions (10.4+).
Another anecdote which may help narrow down the issue: Sometimes the tooltip
shows partial contents from a previously-displayed tooltip. As can be seen from
the following screenshot, the tooltip shows the last few characters of the
#radeon channel topic, followed by a white space and then the alt text of
another channel:
https://www.dropbox.com/s/lsg0walzuvw12of/tooltip_corruption2.png?dl=0
Another user (see IRC log from screenshot above) mentioned that sometimes the
tooltip even shows contents from another process.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3250 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
next reply other threads:[~2015-05-01 3:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 3:08 bugzilla-daemon [this message]
2015-05-01 3:12 ` [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome bugzilla-daemon
2015-05-01 3:26 ` bugzilla-daemon
2015-05-01 3:37 ` bugzilla-daemon
2015-05-01 3:55 ` bugzilla-daemon
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@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.