From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110721] graphics corruption on steam client with mesa 19.1.0 rc3 on polaris
Date: Wed, 22 May 2019 16:26:12 +0000 [thread overview]
Message-ID: <bug-110721-502-rs1JkcNiRq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110721-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #7 from alvarex <edisonalvarez@arnet.com.ar> ---
(In reply to Ropid from comment #6)
> @alvarex:
>
> Try starting chromium with this command line here, it makes it show
> corruption everywhere for me here:
>
> chromium --ignore-gpu-blacklist --enable-gpu-rasterization
> --enable-native-gpu-memory-buffers --enable-zero-copy
> --disable-gpu-driver-bug-workarounds
>
> About Visual Studio Code, I see corruption when I click on the main menu and
> move the mouse around to open and close the different menus there.
no the bug doesn't trigger with chromium unless this error has something to do
maybe chrome is not detecting the gpu (same as steam)
> ac: Unknown GPU, using 0 for raster_config
> [1:7:0522/132124.876161:ERROR:command_buffer_proxy_impl.cc(125)]
> ContextResult::kTransientFailure: Failed to send
> GpuChannelMsg_CreateCommandBuffer.
> [31337:31346:0522/132131.668335:ERROR:browser_process_sub_thread.cc(217)]
> Waited 322 ms for network service
@Ropid
what version of chromium are u using??
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2165 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-22 16:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 22:37 [Bug 110721] graphics corruption on steam client with mesa 19.1.0 rc3 on polaris bugzilla-daemon
2019-05-22 2:41 ` bugzilla-daemon
2019-05-22 12:37 ` bugzilla-daemon
2019-05-22 12:40 ` bugzilla-daemon
2019-05-22 13:57 ` bugzilla-daemon
2019-05-22 14:23 ` bugzilla-daemon
2019-05-22 16:07 ` bugzilla-daemon
2019-05-22 16:19 ` bugzilla-daemon
2019-05-22 16:26 ` bugzilla-daemon [this message]
2019-05-22 16:31 ` bugzilla-daemon
2019-05-22 16:49 ` bugzilla-daemon
2019-05-22 17:35 ` bugzilla-daemon
2019-05-22 17:39 ` bugzilla-daemon
2019-05-22 18:59 ` bugzilla-daemon
2019-05-22 19:01 ` bugzilla-daemon
2019-05-22 19:02 ` bugzilla-daemon
2019-05-23 19:02 ` bugzilla-daemon
2019-05-23 19:04 ` bugzilla-daemon
2019-05-23 19:23 ` bugzilla-daemon
2019-05-23 21:38 ` bugzilla-daemon
2019-05-25 7:54 ` bugzilla-daemon
2019-05-25 9:17 ` bugzilla-daemon
2019-05-29 13:35 ` bugzilla-daemon
2019-05-30 16:21 ` bugzilla-daemon
2019-06-18 21:09 ` bugzilla-daemon
2019-06-25 14:55 ` 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-110721-502-rs1JkcNiRq@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.