If itās in a āNightlyā build it might be wise to wait until another build becomes available, and if the issue persists in the next build, report it on GitHub (IMHO).
Hello.
Long Time Brave user and only recently updated to the latest build. I held off for a while and immediately noticed the downgrade in performance. Reading a lot of this thread I disabled HA and all my extensions and that has kept my CPU usage down. It does spike depending on the website, mostly YouTube. The extensions I had where De-Mainstream YouTube, MetaMask, Captial One. Prior Iād see two Brave Browser Helpers running and a third running on the GPU. So far my CPU use is at 50% if Iām watching any videos on the browser.
Its not a āBrave browser issueā, Some extensions will change over time (various updates or no updates) and will impact performance. Ideally testing a clean browser profile, then testing the various websites. Which will give you a base line, then enable one extension at a time.
Hardware acceleration issues are mainly caused by the hardware and drivers, often on board gpu (laptop) will cause the most problems.
The less amount of extensions the better
Use extensions that are often updated
Update your graphics drivers.
When troubleshooting:
Disable all extensions, and run in private window mode
Clear brave://settings/clearBrowserData, then restart Brave
Test in clean Brave profile
Test CPU usage via ā” ā More Tools ā Task Manager
Depending on hardware, Test video playback in lower resolution (720p from a start)
Test in Brave Beta, which creates a separate profile/sandbox.
I also noticed the same problem compared to previous versions, the amount of lag and performance degradation is insane. Graphics rendering is so slow and the longer you use brave the slower performance it gets. I refreshed and made a new profile which helped but after a few hours of use the laggy performance came back. I have all drivers updated and even tried turning off Hardware Acceleration and no luck.
I went to check out Firefox 93 to see how everything compares and what a huge difference compared to the latest version of Brave, no lag and you can open tons of sites at a time with heavy graphics with no lag, just smooth performance. I tried everything I can think of from making new profiles, reinstalling and no luck.
I also find that after about one hour of heavy usage the performance goes downhill very badly of the entire browser like the browser is failing to clean up memory and do trash collection, I have 64 GB of memory but turning off the browser for a few minutes and turning it back on makes a big improvement.
I can confirm the same problem. Almost 100% of CPU is used with only one tab opened with any website. Problem is mainly in incognito mode. At first problem was only on Brave Nightly, but now, the same thing is on Brave Beta (also incognito window). At the moment that browser (except stable release) is completely unusable.
Iām getting this on the Brave Beta build too - happening only with Private tabs however Iām still getting awful rendering and response times for the normal browser.
From the versions listed above problem is starting for me with version 1.33.28 (and all newer versions) - only in incognito mode. In normal window everything is fine - but when I launch incognito window CPU jumps instantly to almost 100% usage (without any website opened - just opened Private Window).
I am also facing CPU issues
It seems like it keeps one CPU core on 100% constantly. This also happens in private browsing with just a blank tab open. Looks like something is hung, its also only one singular process that causes this (the remaining ones are pretty much idle idle).
No. Extensions doesnāt matter here - on Beta I donāt have any extensions at all and situation looks exactly the same in private window. Also, as I said before, Iāve installed many versions of Nightly and the problem is appearing from certain versions (itās possible that problem is starting even with version 1.33.27, according to @SirObby post, but I havenāt checked - Iāve tried only versions listed by @fanboynz, so I can say that the problem didnāt exist for me before version 1.33.28).
Yes exactly, thatās why I askedā¦ when thereās a contention that no extensions are involved, but you see that in the screenshot (reading carefully, right?) it makes one wonder about the contention.