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.
Since Mattches isn’t adding any other suggestions to my issue, is there anyone else who can help out? Brave Beta is an OK alternative, but doesn’t work smoothly all the time and doesn’t have my bookmarks that I had saved on the regular Brave Browser.
If don’t have it there, then same way he told you where you’ll add --incognito to the end. So it would end up looking something like "C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe" --incognito
Other thing would be similar to above, but trying for a new profile. So it would be --profile-directory="Test Profile" at the end, resulting in something like "C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe" --profile-directory="Test Profile"
Why these steps?
His asking you to download again on top should have repaired anything if there were any corrupt files or any issue on the installation. (Plus helped to make sure we know you’re using the most recent version)
Trying with --disable-gpu should have launched without GPU, in case it was a rendering issue from that.
Checking on Beta helps to make sure it’s not an issue with your computer or chromium in general. If it works there, then we know it’s more isolated to either your profile or version of Brave.
Launching in private just helps to consider extensions and cookies. When you launch in private, it should create a new session with no cookies and with all extensions disabled. If it happens to work when you launch this way, then tells us that’s what it is.
Launching with new profile would launch with a new profile, so everything exceptbrave://flags and changes to custom filters in Shields would be default. If things work fine on that, it indicates it’s something specific in your one profile.
If none of the above works then it indicates something is really screwy. At that point I think would just have to circle back to you mentioning how you uninstalled. May need you to make sure when you uninstall that you select to delete all data as well. But hold off on that for a bit and let’s just focus on the two steps I mentioned today, which is private window and test profile.
Thank you for posting here Saoiray. Launching in a private window made no difference.
Launching with a new test profile shows strange results. At first it would be the same thing. Then I would be able to interact with the browser for a bit before it would freeze up and close itself again. Then I was able to maximize the window without it freezing up. I was also able to click on the “allow” option when the window asked me to automatically send diagnostic reports when Brave freezes or crashes. The browser also isn’t blank anymore; there’s also the counters for trackers and ads blocked, bandwidth saved, time saved and it also shows my bookmarks. I tried to go to a website, but it loads for a bit and ends up crashing.
So I don’t know if this helps in showing what the cause of the problem is.
@J.O.S sorry, had missed your other reply it seems. I’m hoping perhaps @Mattches can follow up with you here. That said, let me just get some clarity on a couple things as well
Question 1:
Ignoring the comment about bookmarks, what are you saying was the issue on Beta? Is it related to this problem or it something completely different?
If it is/was working just fine, then it means it’s likely just something your device doesn’t like about the version of Chromium or Brave that was on it. If it was profile specific we should have seen a change in a new profile, but you’re making it sound like that isn’t really the case.
Question 2:
If you go to brave://crashes are you able to see uploaded crash report ID that you can copy/paste here? Check out Helpful Info & FAQ for Brave Users - #57 by Saoiray if you need to know more on how to see it and in making sure it’s the Uploaded Crash Report ID that is seen and shared. (Copy/paste, don’t screenshot)
Question 3:
An update released today, do you still have the issue after updating?
Question 4:
Did you have any issue using Chrome? If you haven’t tested, please add it and see. Feel free to purge it afterwards but it will be helpful to know if it’s a chromium or brave specific issue.
Other than the bookmarks, so far the only reason is petty, really. When the cursor is on the left or right side of the monitor, scrolling doesn’t work. I know that it’s a beta version, but it seems like a glaring oversight, especially when it wasn’t present in the normal Brave Browser.
Does this require opening the browser and go into the settings? The browser went back to opening a blank page without loading anything and then crashing again. I tried opening it thrice while typing this response and the results are the same.
Edit: I see you type that in on the address bar. No matter, I can’t type anything on it anyway because of the freezing issue.
I don’t know if it has anything to do with the newest update, but it shows the window again to automatically report crashes and my bookmarks, but that’s it.
Brave (normal/release version) at this time launches for a moment, but doesn’t allow you to interact with it and then it eventually crashes — is that correct?
The Beta version of the browser works just fine with the one exception you noted, but outside of that it functions normally?
Launching the browser with a fresh profile and/or private window does not resolve the issue — it still crashes, is that correct?
In the release version of Brave, are you able to view the brave://crashes page long enough to copy the crash report ID there? If so, can you please do so and then share that ID with me here?
I put the command in after attempting to do it a few tries, and then it finally took me to the page. It doesn’t show the Uploaded Crash Report ID. It only shows status and Local Crash Context. If that’s what you’re looking for since the topic on helpful info and FAQ Saoiray linked earlier look very similar, the latest one is 0b2fe215-16b7-4697-88c7-ff0dab807633. I was also able to send some of the latest reports if that helps.
Negative. You should see an Upload Now button or if you pushed that and it’s pending, have to exit Brave and give it like 30 seconds or so to upload. Then when go back it should be up with the Uploaded Crash Report ID.
The difference is crash context usually means it’s still just local on your device and hasn’t been uploaded. Once it has been uploaded and devs are able to see it, then it becomes an uploaded crash report id.
After using much patience, I finally got a Uploaded Crash Report ID. It’s 7e070a00-87b1-060d-0000-000000000000. Before I was trying to send as many as I could, but every time I went to the brave://crashes page, it would still ask me to send now for all of them as if it was never sent at all. Then I realized that if I send just one then maybe it would go through. And it worked! Let me know if you need anything else or if I should get more Uploaded Crash Report IDs.
