-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GUI glitches / artifacts (GPU or driver problem) #3471
Comments
Cant reproduce on Linux. What OS are you experiencing this issue? cc: @brave/legacy_qa |
Mac OSX 10.10.5 |
BTW I've just worked around this issue by turning "Hardware acceleration" OFF in "Settings". Both Beta and Dev. This issue still needs to be fixed. |
I couldn't reproduce this with my However, I managed to reproduce the issue on my VM that's running As @dayfuaim mentioned above, turning off
Added the Looks like this is happening on all the channels. @dayfuaim has this ever worked for you? |
@kjozwiak I can see this on all Beta and Dev, but Release (0.60.45 Chromium: 72.0.3626.109 (Официальная сборка), (64 бит)) is OK with |
@dayfuaim Would you be able to provide us with info from brave://gpu/ we'll need that info to fix this one? |
@dayfuaim Also, if you have a chance, is this an issue for you on release builds of the browser? Thanks for using brave beta and brave dev by the way. We have this reproducing via virtual machine, but we wanted to reproduce on a physical machine. |
@rebron OK, this is
and Beta with HW Acceleration OFF:
|
@rebron Here you go. :) |
@bbondy reproduced on Chrome BETA using the same VM. Doesn't seem to be Brave specific. At least with my case using the VM. Example of the issue happening on @dayfuaim if you have the time, can you download Chrome BETA and see if you can reproduce the same issue that you're seeing? It was most likely reproduced in |
@kjozwiak, I already have Chrome Beta, so that's that: |
Thanks for double checking @dayfuaim 👍 Hopefully someone form the dev team can take a look at the |
@dayfuaim Hi, can you please also share |
@iefremov Yes, of course.
Chrome (HW Accel ON):
|
@dayfuaim Sorry, Denis, the gpu info in your post doesn't seem to be complete. Could you please paste the full info, that can be obtained by pressing the following button? |
@iefremov OK (although I did copied this via button). Chrome (HW Accel OFF):
Chrome (HW Accel ON):
|
@dayfuaim Thanks! And please do the same for Brave :) |
@iefremov Yep, here you go.
Brave Beta (Accel ON):
|
Thanks, @dayfuaim ! I can see that the problem looks similar to #3969. However, Chrome version is older than Brave version, so there is a chance that the next Brave build will fix the problem. @kjozwiak Could you please try to reproduce this in your VM with Chrome 74? |
@iefremov seeing the same thing on my As mentioned above before, I'm not 100% sure how accurate the case really is. In terms of general performance, macOS seems to run very poorly. I'm not sure if that's just due to bad VM GFX drivers? Either way, here's the dump from |
I have the same problem on Linux Fedora (22). My copy of chrome://gpu follows: ... but I am having a hard time to actually paste the info... because everything is mixed. Brave: Version 1.16.75 Chromium: 86.0.4240.193 (Official Build) (64-bit) Problem disappears when hardware acceleration is switched off. |
I have the same issue on my brand-new MacBook Pro 16 inches, I had to disable hardware acceleration… please fix this
|
Just here to say that I'm having this issue as well. Here's my GPU report from
And here it is with it off:
I did check these two reports, and I don't know if this is supposed to happen, but yes, they're different. |
Updated Issue Description (notes from @bsclifton)
There are a lot of combinations of video cards / drivers / etc and Chromium will try to do its best job to resolve these. You can view your GPU related information at brave://gpu
In some cases, users will experience the screen looking unusual- various glitches or artifacts being rendered. For example:
In these cases, we recommend the following:
Use hardware acceleration when available
Please leave a comment or a +1 if you are running into this issue. There are driver allow/block lists which get updated with each version of Chromium - so if you had an issue, there's always the possibility that it has been fixed. An example of the two lists (on brave://gpu under
Version information
:You can toggle HW acceleration and see if it works OK. Using hardware acceleration is preferable because the browser will offload rendering operations to the graphics card instead of using the CPU
Tracked upstream in Chromium with https://bugs.chromium.org/p/chromium/issues/detail?id=1068170&q=gpu%20artifacts&can=2
Original Issue Description
Search suggestion panel is not fully visible while typing in omnibox.
Moreover, sometimes there are some graphical artifacts (see screenshots in "Actual result").
Steps to Reproduce
Actual result:
Beta:
Dev:
Expected result:
Search suggestions are visible fully as usually and without artifacts.
Reproduces how often:
Always.
Brave version (brave://version info)
0.61.36 Chromium: 73.0.3683.39 (Официальная сборка), beta (64 бит)
0.62.7 Chromium: 73.0.3683.39 (Официальная сборка), dev (64 бит)
Reproducible on current release:
Website problems only:
Additional Information
This issue starts happening only in latest Brave Beta/Dev. Not in previous builds.
The text was updated successfully, but these errors were encountered: