Just today, Brave starting using so much energy that my MacBook Pro M3 Max started overheating. Had to disable and go back to Chrome.
Does your issue have a similarity with some of the details in the description at(?):
Yes, quite close. But it doesn’t need You Tube videos to happen. Simply sitting idle if a web page has any video at all, such as Wall Street Journal, Barrons, etc, running in a window, the CPU usage spikes to 100 - 150%, and the laptop get quite warm to the touch. It also happen with Chrome. But not with Safari. Safari typically runs at 97 - 99% idle.
Sadly, I’d really like to use Brave for its handling of most web pages and ad suppression, especially You Tube.
I hope this helps.
Thanks for bringing me into this. I also would like to keep using Brave but am starting to think that I won’t be able to as I can not find a solution
I might use it for the few things it does really well, and shut it down otherwise, but not as a default browser.
Yeah I’m in the exact same boat, I love Brave but it’s causing my machine to overheat and haven’t yet found a solution apart from switching to Chrome.
I am adding 3 more MacOS-Brave Browser-users performance issues (sluggish, overheating, troubles with installing, updating), because of some questions I have about available disk space aka drive space on MacOS computers.
-Brave detected as InfoStealer in Mac Analytics Logs
-Brave crashing after update please help
To get started, please use the following Apple instructions for starting up the Mac in Recovery Mode, and then selecting the Disk Utility. With Disk Utility, select the boot volume of your Mac, that you usually use and has Brave Browser installed.
Be sure to choose the appropriate hardware - Apple Silicon or Intel - for your machine:
-https://support.apple.com/en-us/102518?choose-your-type-of-mac=mac-with-apple-silicon
[Hand writing:] Write down all the disk / drive data info that you see - all of it, in detail, and then report your findings.
Because, all of the issues’ symptoms, can point to a lack of ACTUAL available disk / drive space. And, using the specific Disk Utility of the Recovery Mode, is your easier, more reliable procedure for getting the info.
Yes…I’m running an M3 Max with 48 GB and 16 cores. And it overheats with any web page that’s running a video. The case actually gets very warm to the touch. Chrome may not help if Brave is based on it. Safari doesn’t seem to have the problem.
Yeah you’re right, I’ve had the crashing issues happen when I switch to Chrome too. It must be an upstream Chromium bug, also it’s not just YouTube, my system overheated when I hovered Instagram videos as well.
Regarding the power hogging, it’s a specific process within Brave — something like “Brave Content Helper (rendering)”. You can see it in MacOs ‘activity monitor”. When called, it runs the CPU to over 100% and holds it there. If you forcibly end the process, the CPU usage goes back to normal. For me, the problem has only come up recently. It might be from the latest upgrade, but it’s less than a week old.
Yeah for me it’s the same, Brave Content Helper (rendering) is the CPU hog and yes it began with a recent upgrade. But I do think it might be a Chromium thing because the same thing happened on Chrome and the activity monitor showed a similar process running but just the Chrome version.
You might be right about it being a Chromium thing. However, Chromium is an open source distribution, so, if they’ve got some decent coders, they should be able to fix it or get Google to. Because it’s so widely used, it’s hard to avoid the problem. I haven’t seen it in Safari, but I have in Chrome, Opera, and Brave.
Hopefully Brave will see this thread.
I thought the same, however the same things then happened to me when using Safari. Also, it then happened when only using spotify and everything else was closed!
Can anyone here confirm whether or not disabling Graphics Acceleration resolves the issue? Settings --> System --> Graphics acceleration
One thing to try. Safari lets you adjust settings for any specific web site. You can set it to prevent “auto play”, so those videos they sometime embed won’t run, which might trigger the process.