Description of the issue:
Starting Sunday I have problems using Brave. I uninstalled and reinstalled the browser, but nothing changed. Sometimes a prompt appears to send a diagnostic report but it doesn’t respond when I click on it and then the web browser closes itself. My computer also slows down with the disk usage going to 100% while the browser tries to open.
Steps to Reproduce (add as many as necessary): 1. 2. 3.
Opening the browser from the home screen. It’s as simple as that.
Actual Result (gifs and screenshots are welcome!):
Brave Browser opening a smaller blank window and becomes unresponsive. Around a minute or so it closes by itself.
Expected result:
Brave Browser opening full screen showing home screen and able to interact with it with no issues.
Reproduces how often:
Every time I try to open the browser since last Sunday.
Operating System and Brave Version(See the About Brave page in the main menu):
Windows 10 Operating System. Brave version unknown due to being unable to check settings.
Additional Information:
I also use Brave on my phone and I have no issues with it.
Find the shortcut for Brave (generally on Desktop), right-click and select Properties from the context menu.
Click into the “Target” field, and type --disable-gpu at the end of the path. Note that you must type this outside of the quotes with a space between the flag and quotes.
The Brave Beta Browser is working. I see this as a temporary fix however because it didn’t really solve why the regular browser isn’t working for me. Is there something on Brave Beta that isn’t on the official Brave browser?
This just means that the issue you’re seeing has something to do with the specific profile you’re using in the stable build of the browser. I would wager this might be due to an extension you have installed at this time.
Here is what I recommend you try next:
First, visit brave.com/download and redownload and run the Brave installer — it will detect that you already have a version on your machine and will simply fetch and apply the latest updates to the browser. I suggest this because we have released an update to the browser yesterday and there is a chance that this issue gets resolved simply by updating to the latest build.
If the above doesn’t work and you have any extensions installed in the browser, I suggest you try launching the browser with extensions disabled to test and see if one of them may be the cause of the issue. You can do this the same way you launched the browser with the --disable-gpu flag, but instead use the flag --disable-extensions.
If you do not have any extensions installed and/or nether of the above suggestions resolve the issue, please let me know and we can try other troubleshooting options.