-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Brave 139.111 extremely laggy with hardware acceleration enabled (Nvidia) #23254
Comments
This is still an issue with the latest Brave version (1.39.122) |
How is it possible that all of these issues with hardware acceleration keep being down-prioritized? They are triaged, tagged as priority/P5, or just downright ignored... I would like to mention one thing, though. Because I actually got this working. Has a lot of issues with Brave specifically being slow. I had forced a 122Hz refreshrate for all applications using "RivatunerStatisticsServer". So I added a profile for "brave.exe" which essentially disabled Rivatuner for that application. I also have/had "Fast-Sync" enabled globally (so a type of V-sync) in the Nvidia Control Panel (or specifically with NvidiaProfileInspector). I think I only changed the Rivatuner setting, as I still seem to have "Fast-Sync" for brave.exe in NvidiaProfileInspector. But this has at least fixed it for me. |
@Fooughhy I also have a high Hz monitor (144Hz) with Freesync (or as Nvidia calls it, 'Gsync Compatible'). Just tested setting V-sync to 'off' for Brave in Nvidia Control Panel, and setting Hardware Acceleration to 'on'. I still get janky scrolling. |
Just to confirm, did you restart brave in-between? And also, do you have any other framerate-limiters enabled? |
I have found the culprit! (I did restart Brave inbetween beforehand, but your frame-limiter question did it). Global 'Background Application Frame Rate' is set to '60'. Setting it to unlimited fixes the problems. It seems that, unlike Edge or Chrome, Brave reports itself as being a background application even when in focus. |
Wow, nice that you got it working! I had no idea that was the explanation for the issue though. But yeah, that explain why other browsers works fine at least! Nice man 👍 |
cc: @atuchin-m @iefremov |
I have a laptop with intel cpu (i7-7700HQ), nvidia (gtx 1050) and intel integrated gfx card (hd graphics 630). |
@424344 I do not think this is correct. You would want to use your actual GPU for the hardware acceleration, and not the CPU. I may be wrong, but I don't think the integrated GPU is actually active when you have a dedicated GPU as well. So this seems weird. I guess you are using a CPU for hardware acceleration in this case? To add to this, I would assume your issue was fixed because it is the combination of Nvidia GPU and Brave that causes the issue. |
I believe that I'm not using the cpu, but the gpu that intel integrated into the cpu. |
Hi. I have noticed the severe lagging of the browser after AMD and NVidia driver updates. I have followed the advice of disabling hardware acceleration in Brave, which fixed the issue. Then I did some digging and saw that my AMD graphics were disabled in device manager for some reason. After enabling it again, I switched the hardware acceleration back on and everything runs as smoothly as before. As to why that is, I haven't the faintest, but I'm hoping it will shed some light on the issue for the more enlightened among us. |
Holy cow, this is the kinda solution (better than none) |
This is still an issue on 1.51.110 lol. But just so anyone new who finds this thread knows. This is caused by Background Application Max Framerate on NVIDIA. Change the option in program settings to off and restart brave to fix it. Wish I found your post about this, would've saved me my troubleshooting adventures. This issue has existed for almost a year now apparently. Edit: |
Hello and thanks you ! I had the same problem and this option solved it. My laptop is an XMG Fusion 15, Intel Core i7-9750H, 32 GB RAM + NVIDIA GeForce 1660 Ti Mobile |
Same issue here with Version 1.58.137 only on Brave, it works fine in both Chrome and Edge. |
same issue here |
same issue here with RTX 3080. |
I had been having this problem on Brave, Vivaldi, LibreWolf, Opera GX for years. This was the reason I quit using these, I could only use Ungoogled Chromium and official Firefox. Can't believe it existed because of this setting, thank you. |
I finally found a fix for this issue with a Hybrid GPU Setup, I urge the Brave team to apply this solution to people using hybrid setup or at least provide a section like "Nvidia common issues" in the download page and refer to the solutions provided in this thread. I had the program settings in Nvidia control panel greyed out, to enable them I had to switch to Ultimate mode in Armoury Crate app from ASUS (this requires a reboot and switches completely to the NVIDIA GPU), then I could change the settings with NVIDIA Control Panel, but I found that Background Application Max Frame Rate was disabled by default, so I switched back to "Standard" mode again which uses MSHybrid technology provided by Windows and the one causing the issue with Hybrid Setups because Windows decides to use the NVIDIA GPU with Brave while others Web Browsers, Windows don't use the NVIDIA graphics card by default. To fix this issue you have to go to the settings app, System > Display > Graphics, add Brave to the list and choose Power Saving (which uses the intel graphics) and restart the app if you had it opened. Now I have a very smooth experience with hardware acceleration enabled in Brave. If you ever decide to use the NVIDIA GPU with Brave, you should switch to "Let Windows Decide" or "High Performance" but the issues come back unless you plug in the laptop which switch enables the Nvidia Graphics Card and everything works fine. I'm not sure if you can automate this on the brave installer, but a FAQ for NVIDIA Users in the download page would be useful and surely bring a ton of users back to Brave. |
microsoft/vscode#107016 (comment) and BrowserWorks/Waterfox#2979 (comment) speculate other browsers may be working not because of some better implementation or practice, but just because they are being special pleaded by dedicated app profiles. Does it make any difference if you rename brave's executable to |
Renaming brave's executable to chrome.exe did the trick for me! |
A quick and dumb grep showed the executable names inside igd10um32xe.dll/igd10um64xe.dll, igdgmm32/igdgmm64.dll and IntelControlLib.dll/IntelControlLib32.dll. |
can confirm this is still an issue, unfortunately had my NVME with my OS on it implode last night, after re installing everything, i usually have youtube running on my second monitor while gaming on the primary, had Destiny 2 open while watching videos, the video would stutter, only thing that solved the issue was disabling hardware acceleration in Brave, no max background set in nvdia, gsync if off and im running 165hz refresh on both monitors. |
I can confirm renaming brave.exe to chrome.exe FIXED all the issues. The GPU is properly selected when I run brave. I tested it on a clean Windows 11 Installation with no changes made to the Windows Power Settings. I want to add that before renaming it to chrome.exe I tried to add brave.exe to the Google Chrome profile with the NVIDIA Inspector and this DID NOT FIX the issue. Please @rebron @iefremov reconsider renaming brave.exe to chrome.exe as you did in the past and update brave as soon as possible, I've seen a lot of people not using brave because of a ton of GPU related issues because of this NVIDIA Profile bs. I found that you already renamed brave.exe to chrome.exe in the past, why did you revert it? |
Because it's literally mentioned and linked there? They just renamed the gpu process, perhaps they are missing another. Separately, an additional idea to help would be to use profile inspector to check on chrome's knobs, to see which one is responsible for the magic when applied to others. |
use the method in the issue is the correct way to solve this, instead of changing background frame rate higher. |
I know this is not your area and I hate to keep tagging you like this occasionally, but in the past you've been angels in getting issues alerted to the proper team. On top of that, the "workaround:disable-hw-acceleration" tag is wrong, I'm not sure if you have the rights to remove that. |
@ahydronous can you try running brave with |
@iefremov here are the reports for both, ModuleFileNamePatch argument and without it. The issue is still there, the NVIDIA GPU is automatically used when I open brave, this doesn't happen with any other Chromium browser or Firefox. Tell me if I can provide you any other information, please. |
I've been using Brave v1.68.131 for a couple of days now, and I haven't noticed this bug. Brave is using the integrated GPU. I haven't set Brave to Power Saving mode in the Windows graphics settings either. Can anyone check if the issue is fixed on their end, too? |
@iefremov I don't have access to an Nvidia GPU atm (long story). @geekyBoogiepop do you have Background Max Application Frame Rate set to 60? If not, you are talking about the separate issue of a hybrid GPU setup. Perhaps it would be better to create a separate issue for that, although if it is fixed, that won't be necessary haha |
@ahydronous False alarm. The issue happened today, again, it is not fixed, who knows what happened during the last two days. |
This solved the issue, thanks! |
This worked for me. Thanks for pointing that out. Just to re-iterate for those who don't have the full context. This setting is found under the NVIDIA Control Panel, Select Manage 3D Settings. Then on the right Pane, select the Progam Settings Tab, select the Brave (brave.exe) program, if its not in the list simply click "Add" and browse to your Brave browser installation path (Default install path is C:\Program Files\BraveSoftware\Brave-Browser\Application\Brave.exe). Scroll down to "Background Application Max Frame Rate" and change the setting from "Use global setting (on)" to "Off". Restart the browser and test. Note: Keep note of this setting as I've seen occurences where updating the Nvidia drivers may reset some application specific settings to their default value, it shouldn't be an issue but if you see the problem happening again after Nvidia driver update, double check to be sure. Cheers! |
I am having the same issue on Linux, when I resume scrolling after idle cursor for a few seconds e.g. when reading. I have AMD 6800 though. Disabling Hardware Accelaration resolves the lag, but that's not a profer fix. |
happens to me too (win10) but my laptop has an intel gfx card (intel hd graphics 630). since it's not an nvidia I cannot fix it with the workaround using nvidia control panel. should I file a new bug report for intel gpu? |
Linux has nothing to do with this, yeah (which is already stretched enough by mixing the profile issues of different vendors on windows) |
Yes, and obviously even GPU type doesn't matter, since the problem persists among all vendors (Nvidia, AMD, Intel) |
You guys are wrong. This is an issue specifically with Nvidia not whitelisting The other issues you are speaking to are not related to this issue. Please open up separate issues for them. |
The problem is very much specific to manufacturers, since it's not the OS that is doing anything wrong. And in fact there isn't even a single report of AMD problems (no, linux doesn't count, both because it is broken itself but also because all drivers but nvidia's are shared). It would be nice if somebody could check my aforementioned profile inspector/hexediting hunches though. |
Description
Since the latest Brave update, my browser has been extremely laggy when scrolling an watching video. The latest Edge or Chrome do not have this issue. I am on Windows 11.
Steps to Reproduce
Actual result:
Laggy browser
Expected result:
Smooth browser
Reproduces how often:
Always
Brave version (brave://version info)
139.111
Version/Channel Information:
Stable 139.111 and Nightly 141.33
Other Additional Information:
Miscellaneous Information:
I run an Nvidia 3070Ti with the most recent driver (512.95)
Turning off 'Hardware Acceleration' fixes the extreme lag
The text was updated successfully, but these errors were encountered: