Skip to content

GPU issues incident reports

Jump to bottom
Brian Clifton edited this page Jul 3, 2019 · 18 revisions

This wiki intended to track the problem(s) that folks are experiencing and what steps we've already done / need to do. Will fill this in with more details

Reported customer incidents

GPU taking too much power (using discrete not integrated)

Work-around suggested by support for these folks has been to disable hardware acceleration, which seems to address the problem.

  • https://twitter.com/brendaneich/status/1146191407725441025?s=12 (macOS / 0.65.121)

    Can you please make Brave not eat so much battery on my MacBook Pro? Seriously, just eats battery like a hungry thief, I need to use Safari instead.

  • https://github.com/brave/brave-browser/issues/4858 (macOS / 0.65.118)

    When GPU hardware acceleration is enabled (which is the default) it occurs that some browser window is enabling dedicated GPU (if you have an MBP 15 for example). Which is fine, a lot of modern web pages need that extra power for fancy things. But if you close that window or tab, Brave doesn't switch back to the integrated GPU. So you stay at using the dedicated GPU, which burns your battery. Chrome or other Chromium based browsers do switch back after some time, Brave doesn't.

  • https://community.brave.com/t/brave-wont-change-back-to-integrated-gpu-and-high-battery-usage/47295 (macOS / 0.60.47)

    I have a problem with GPU usage in macos Mojave. When a webpage activates the dedicated GPU it will never go back to the integrated GPU when the webpage is closed. This then reflects in a much higher battery usage. I checked on chrome using the same webpages to trigger the dedicated GPU, and when I close them, always revert automatically to the integrated.

Bad Web GL performance

Whilst playing around with some WebGL 2 code I noticed that fps seemed to be roughly half of what Chrome was chucking out. Rendering 2 million cubes produced around 29fps whilst in Chrome it easily hit 60fps.

A while ago when it first released, I tried playing Minecraft Classic in Brave but it was very laggy and basically unplayable. I thought it was an issue with that specific game until last night when I released a simple game I made with a WebGL version and I tried to play it in Brave but it was extremely slow, especially when going into fullscreen mode

GPU related artifacts

Basically rendering looks wrong (or not at all). Extremely slow performance. Work-around has been for users to disabled hardware acceleration (either in UI or via --disable-gpu command line flag).

My Brave experience has become so horrible. A new tab takes 3-5 secs, typing in the url bar has a lag of multiple seconds. While typing, the window turns to garbage. I deleted ~/Library/Application Support/Brave* and reinstalled and it's the same. ... It's only a brave issue and for me it didn't start until the Dev release w/ ads (0.63.x).

Search suggestion panel is not fully visible while typing in omnibox. Moreover, sometimes there are some graphical artifacts (see screenshots in "Actual result").

Screen text garbled unreadable.

totally blank user interface. only visible is popup menu (when right clicking) all other browsers are working correctly (chrome, opera, firefox)

Whenever I open the browser, strange text fragmentation can be seen. It sometimes happens when I open the site, sometimes only after I interact with it. This isn't contained to website, also Brave intern sites like the settings or the DevTools are affected. Also on scrolling the text flickers into different fragmentations.

On many sites, text is showing as glitched/half showing. I've had this issue since moving to muon

Things that have been done which may help

Field trial config was changed in 0.68.x

This would ship to release channel on August 20th. Work was done in the following PRs:

Untriaged list of links / occurrences / etc that should be looked at

Actions we can take (help needed)

  • Values that were changed with the field trials should be examined. This config change will make us more closely match Chrome/Chromium. We may have had a flag enabled which made Brave prefer the discrete GPU - or perhaps we had a flag on which bypassed the driver blacklist
  • Triage the above occurrences and break down by OS / Brave version
  • Find more occurrences and triage
Clone this wiki locally