-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
GPU-related artifacts #3969
Comments
GPU logs from Chrome and Brave (note different versions). |
@bbondy @bridiver @BrendanEich |
@rebron please triage |
Similar picture is in #3471 (comment) |
@larseggert if you run into this again, you can try disabling hardware acceleration under brave://settings/system It would also be great to know more about your setup - are you on a newer core i9 MacBook? we have seen some errors with those where HW acceleration needs to be disabled for now I've looked in detail and we're matching Chromium on everything, minus using finch experiments (ex: fetching blacklisted drivers from server) |
It’s a max’ed out 16” MacBook, running on discrete GPU, since I have a large external monitor attached.
I think this is actually a Chromium issue, when it happens in Brave it also happens in Chrome. |
I'm also encountering this issue. `
I'm encountering the issue on several different websites at the moment. Artifacts present at the top of the Mentions section. I've reproduced on at least 3 different occasions in Google Sheets. Will disable hardware acceleration and report back if I reproduce the issue. |
Disabling hardware acceleration solved the problem, but created a new problem where certain web pages that were using it are extremely slow. |
The issue still persists in Version 1.14.81 |
1.16.67 still present, restart of the browser solves the issue though. No need to reboot.. |
+1 from Community https://community.brave.com/t/display-glitches-after-a-while/181318?u=eljuno You'll find similar reports on Community. |
Closing as duplicate of #3471 |
Description
From Twitter: https://twitter.com/JohnMarkoff2/status/1111299290268196864
More details in the thread
The text was updated successfully, but these errors were encountered: