Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.
Delete the any text above the line separator below before posting
Description of the issue:
I started having trouble with Brave crashing when I loaded certain websites (amazon.com, slashdot.org, don’t remember the others). I stopped using the browser for a few days, and then when I clicked a link, it opened in Brave and the page worked fine, browser didn’t crash. Thought everything was somehow fine again and tried loading slashdot.org in a new tab; immediate crash.
Which sites cause it to crash seem random. Slashdot and Amazon are consistently a problem, whereas ArsTechnica.com and MacRumors.com are consistently not.
I ultimately tried nuking Brave and starting over. I followed the instructions from Brave on how to completely remove it.
How can this issue be reproduced?
deleted both the app and the Brave folder in ~/Library/ApplicationSupport and emptied the Trash.
I then downloaded the latest version via Firefox and dragged it into the Applications folder
Opened Brave and, before doing anything else (signing into sync chain, adding extensions, etc), I opened Amazon.com. Immediate crash.
Expected result:
Fresh, stock installation would remove the issue, leaving me to either A) re-sync my stuff and go on my merry way or B) re-sync and figure out what within my extensions (or other stuff?) was causing the problem.
Actual result:
Fresh, stock installation of the app crashed when I tried to open amazon.com
Brave Version( check About Brave):
Brave is up to date
Version 1.73.91 Chromium: 131.0.6778.85 (Official Build) (x86_64)
Additional Information:
macOS Sonoma 14.7. Problem started close to a week ago.
Ok, I finally got a chance to try all of that as well. No change. Loading slashdot.org causes the browser to immediately crash.
I also previously tried deleting all local data for my profile (no bookmarks, extensions, sync chain, etc) and then deleting the app and reinstalling, but it still crashes on what seems to be a completely fresh installation… Any ideas?
Just tried fully nuking it again (deleting the app, ~/Library/Application Support/BraveSoftware/, ~/Library/Preferences/com.brave.browser.plist), re-downloading and installing a fresh copy of the app, and then going to slashdot.org without loading any personal preferences or info of any kind. Immediate crash.
I feel like there is some other file(s) I need to delete that Brave has neglected to mention that is causing the browser to puke (unless it’s a bug in the current builds of the browser??). Maybe some support file somewhere that Brave uses is corrupted and is causing the crash on some sites, or maybe sites that use a certain piece of javascript or CSS or something trigger a bug and produce the crash?
@fourquarts I see you’ve done some things like try to uninstall and all, which may make some thing I’m going to say feel like unnecessary or unhelpful, but do work with me a bit here. Just hoping you can check on things using each thing as a separate step. If step 1 doesn’t work, revert back and go to step 2 and continue as such.
Does it happen in private window?
If you create a new browser profile, do you notice any difference.
Have you changed anything at brave://flags? If so, please put it back to default and try.
Assuming Brave is actually crashing, can you share the uploaded crash report ID for the most recent crashes? Instructions on how to do this is at Desktop and Android Crash Reports
@Saoiray Hi - thanks for responding. Here’s what happened each time (nuking everything in between each step):
Yes, crashed
There was no profile once I nuked it (other than the default “Work”), but I created a new one anyway. Yes, crashed.
No, I don’t think so, but I reset it anyway. Yes, crashed.
Just downloaded Brave Beta and yes, crashed.
To my surprise, yes, Chrome crashed when I tried loading Slashdot. Brave has been my daily driver for years now, so I’m surprised this is happening in either one. Might this mean that it’s an upstream bug?
Seemingly, each time I nuked everything, the crash report list was deleted, but here is the one from the most recent crash (Brave, not beta). For some reason, it hasn’t uploaded yet, so I hope the upload ID is the same as what I have here:
### Crash from Wednesday, December 4, 2024 at 12:03:19 AM
|Status:|Upload requested by user|
|Local Crash Context:|f296898c-af43-40d1-888f-7f43dd2aa32c|
Since it is happening in Chrome then it definitely is an indicator that it is an upstream issue that would have to be resolved.
Not quite what’s needed—they would need the uploaded crash report ID.
From what you’ve shared, it looks like you’ve requested the crash report to upload, but because you haven’t exited Brave yet, it hasn’t actually been uploaded. For some reason, crash reports won’t upload while the browser is running. Typically, you’ll need to exit Brave and wait for about 30 seconds or so for the upload to complete.
The crash context ID is only for your local state. The uploaded report ID, on the other hand, is what’s required because it confirms the report has been submitted to Brave. They can then use that ID to reference and analyze the crash report.
@Saoiray Ah, ok. Quit and opened the browser again, and it now shows that the report was uploaded:
### Crash from Wednesday, December 4, 2024 at 12:03:19 AM
|Status:|Uploaded|
| --- | --- |
|Uploaded Crash Report ID:|38ae1800-857e-fd0c-0000-000000000000|
|Upload Time:|Wednesday, December 4, 2024 at 12:19:39 AM|
