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.
There is already an entry in the community forum which describes that:
https://community.brave.com/t/brave-wont-change-back-to-integrated-gpu-and-high-battery-usage/47295
And turning off hardware acceleration is more or less just a workaround then a real solution to this problem.
And opening the in-browser task manager to kill the GPU process isn't nice as well...
If you install a tool like gSwitch ( https://github.com/CodySchrank/gSwitch ) you can see which GPU is currently in use.
Dedicated GPU stays active
Brave should switch back to integrated GPU
Brave 0.65.118 Chromium: 75.0.3770.80 (Official Build) (64-bit)
Confirm this is an issue. My system is 2015 MacBook Pro w/ discrete GPU.
Confirm this is still an issue on:
Version 0.66.100 Chromium: 75.0.3770.142 (Official Build) (64-bit)
Tested using MacBook Pro mid 2015 with this graphics config:
I saw this issue as well:
0.67.125 Chromium: 76.0.3809.100Â (Official Build)Â (64-bit)
Testing on 2019 Macbook Pro:
Radeon Pro Vega 20 4 GB
Intel UHD Graphics 630 1536 MB
Confirming on a MacBook Pro (Retina, 15-inch, Late 2013). Makes my legs pretty hot.
Version 0.68.132 Chromium: 76.0.3809.132 (Official Build) (64-bit)
On Surface Book 2 15" (Windows 10, Insider Preview), same issue is happening: Merely launching Brave (v1.0.0 Release Channel) spins up the dedicated GPU to the tune of 50-60%.
Contrast with Edge Dev and Firefox Dev Channel: Neither has this issue, and both properly use the integrated GPU.
Confirming this is still an issue.
Macbook Pro (Retina, 15-inch, 2016)
Version 1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)
Same issue happening
Macbook Pro (Retina, 15-inch, 2017)
Version 1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)
Confirmed for:
Macbook Pro (15-inch, 2018)
Version 1.0.1 Chromium: 78.0.3904.108 (Official Build) (64-bit)
Confirmed for:
Macbook Pro (16-inch, 2019)
Version 1.0.1 Chromium: 78.0.3904.108 (Official Build) (64-bit)
And this is indeed pretty annoying!
Not sure if I have the same issue but I have made the experience that my battery is dead after using VS Code + Brave for 2-3 hours. When I use VS Code + Safari the battery lasts 8-9 hours as expected. No compiling or any other "heavy CPU work" was done in these few hours. Battery was always 100% before
macOS Catalina 10.15
MacBook Pro (15-inch, 2014)
Version 1.0.1 Chromium: 78.0.3904.108 (Official Build) (64-Bit)
Confirmed for:
I was wondering what was eating my battery life...
Confirmed for:
Actually it got fixed for me since the last either mac os or brave update
Upd: No, it is not fixed!
Interesting, my Mac and Brave are fully up to date too, but it is definitely still happening.
To test you can view the new iPhone SE page https://www.apple.com/uk/iphone-se/ and do some scrolling, which immediately utilises the discrete GPU. Then close the tab and it does not stop using the GPU until you either restart Brave or use the Brave task manager to kill the GPU process
not fixed for me.
after 30min working on brave :

I only have 5 tabs opens (Gmail, google drive, gsheet, gdocs)
I can't use brave anymore
My config :
MacBook Pro (Retina 15 pouces, début 2013)
macos 10.15.4 (19E287)
Version 1.7.92 Chromium: 80.0.3987.163 (Official Build) (64-bit)
Ok, I take my words back. It is indeed not fixed for me as well…
I love brave but I think I'm off to firefox. My legs are on fire :-(
The issue is still here, Brave please take it seriously. I want to fully switch to Brave, this is one of the many hassle preventing me to do it
Most helpful comment
Confirmed for:
I was wondering what was eating my battery life...