Dear community,
I’m having CPU issues as described earlier on in similar topics but found no real solution to the issue.
Specs:
MacBook Pro (MacBookPro16,1)
6-Core Intel Core i7 with 2,6 GHz
macOS Monterey 12.6
Brave 106.1.44.108
Symptoms:
Brave consuming huge amounts of CPU% causing the MBP fan to blow at maximum speed and draining my battery when not on charger.
Tried (with no difference):
Closing down substantial amount of windows/tabs + Reboot
Hardware acceleration on/off (HWA) → no difference
Hoping to receive some response from Brave team as well…
KR, Sander
Hi @sandermulder
Thank you for reaching out and for the detailed report, sorry to hear you’re having trouble with Brave Browser. Can you try disabling Hardware Acceleration
in settings
to see if this resolves the issue?
You’ll find this in Settings --> Additional Settings --> System --> Hardware Acceleration.
Please let me know if that works and have a nice day!
Dear @Alice2095 ,
Thank you for your suggestion. Naturally I tried this option but this does not seem to make any difference.
Any other options in mind?
KR, Sander
Update Brave to the latest? Brave 106.1.44.108 seems pretty old.
Dear @fanboynz ,
Thanks for your suggestion. As far as I can see, I run now Version 1.45.113 Chromium: 107.0.5304.62
Any other suggestions in mind?
KR, Sander
Specific pages causing CPU usage? Also Disabling HW Acceleration = Increases CPU usage.
Test in private window mode, no extensions
Test in new Brave profile
Check using brave task manager (right on the top bar to open) which website or process is the culprit and have a look at the bug report. Might be similar?
Hi
Intel Mac
MacOS 13.0 (problem was present in lower version too).
Brave browser Version 1.45.116 Chromium: 107.0.5304.91 (Official Build) (x86_64)
Steps to reproduce :
Goto global shield settings in brave, change tracker protection to “Aggressive”.
Open the problematic website.
Confirm the usage in the task manager. CPU remains in high 80s continously for as long as the website is open.
Changing the global shield to “Standard” and then refreshing the page solves this issue.
Weirdly, swit…
system
Closed
November 29, 2022, 5:43am
8
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.