![]() ![]() The first - adblock cosmetic filtering - can reduce CPU thirst. If this test works, then go to, and ENABLE both:īrave://flags/ #brave-adblock-cosmetic-filtering The idea, here, is to somehow get Brave Browser running, from the command line, and using flags that might reduce its thirst for CPU/RAM. But, the remaining command line character strings for each, are the same, after the process name:īrave -n -args -disable-gpu -enable-leak-detection -crash-on-failure -incognitoīrave-browser -n -args -disable-gpu -enable-leak-detection -crash-on-failure -incognito I do not have a Linux machine available, and I’m not quite sure if “brave” or “brave-browser” is the correct process, here. one of two slightly different Linux commands for starting Brave Browser from the command line. In another terminal window, you might also try. In a terminal window on your Linux machine, the following command might show the Brave Browser processes (if I wrote the following correctly):Įven though Brave Browser is not yet running, leave that terminal window open/running. Quit everything and restart your Linux machine. ![]() If you are willing to somehow still take a whack at making the “old beater” run. ![]() My GPU belongs to the GTX 10 series - NVIDIA Proprietary Driver. Linux (Arch / AUR brave-bin) seems to be either immune or less affected. This issue only happened to me on Windows 10. I expect the browser to not hard crash my computer or freeze it temporarily. I suspect it to be related to hardware acceleration and GPU spikes but cannot confirm it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |