Brave browser latest version crashing randomly

Description of the issue:
How can this issue be reproduced?

  1. Browser randomly crashing
  2. It happens many, many times, on random occasions, and for the last few updates, it continues to happen to me.
  3. Operating System: EndeavourOS

KDE Plasma Version: 6.4.0

KDE Frameworks Version: 6.15.0

Qt Version: 6.9.1

Kernel Version: 6.15.3-arch1-1 (64-bit)

Graphics Platform: Wayland

Expected result:

Brave Version( check About Brave): [Brave 1.79.126 (Official Build) (64-bit)]

Additional Information: I tried all of the general things, restart, reinstall (clean), didn’t work out

Thanks for writing in. Can you share your Crash ID’s? They can be found at Brave://crashes

Thank you for replying this is the only text there

Crash from Tuesday, June 24, 2025 at 11:11:22 PM

Status: Not uploaded
Local Crash Context: d31f22a3-97fe-41b6-ae0b-43cc0503a4c4

@Sakalabujhan You need to first send the crash report before providing the ID – the ID (after it’s submitted) should show all 0’s at the end:

I’m so sorry I didn’t knew:

Crash from Tuesday, June 24, 2025 at 11:11:22 PM

Status: Uploaded
Uploaded Crash Report ID: 25102500-3b0c-090e-0000-000000000000
Upload Time: Tuesday, June 24, 2025 at 11:56:33 PM

Thank you for the report – I’ve forwarded this to our devs for review. Hope to have more information for you soon.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Description of the issue:

This happens mostly when I just open the browser after turning it on, and sometimes when I open two profiles at the same time.

How can this issue be reproduced?

It randomly happens, but at least a few times per week, it’s super annoying. I’m planning to move back to Chrome. Seriously, it’s frustrating.

Expected result:
browser crashing

Brave Version( check About Brave):

Brave 1.80.124 (Official Build) (64-bit)

Chromium: 138.0.7204.168

Additional Information:

Operating System: EndeavourOS
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor 1: Mesa Intel® UHD Graphics
Graphics Processor 2: NV138
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: VivoBook_ASUSLaptop X531FLC_S531FL
System Version: 1.0

Crash report:

Crash from Saturday, July 26, 2025 at 1:34:30 PM

Status: Uploaded
Uploaded Crash Report ID: cc450600-bf2d-370e-0000-000000000000
Upload Time: Saturday, July 26, 2025 at 1:34:32 PM
Local Crash Context: 9e5d61fd-ae4f-4c72-8e8d-b6f9cf2aa0bd

Crash from Friday, July 25, 2025 at 9:19:05 AM

Status: Uploaded
Uploaded Crash Report ID: 6e420300-bf2d-370e-0000-000000000000
Upload Time: Friday, July 25, 2025 at 9:19:07 AM
Local Crash Context: 2156a0b6-52cc-4e68-a993-eb2e3d1857cd

Crash from Thursday, July 24, 2025 at 10:44:37 AM

Status: Uploaded
Uploaded Crash Report ID: ad3f0100-bf2d-370e-0000-000000000000
Upload Time: Thursday, July 24, 2025 at 10:44:39 AM
Local Crash Context: 6b01e685-78a2-42e6-9341-32d4fd4ca042

@Evan123

OP has Crash ID numbers.

1 Like

Thank you for reporting! I’ve sent to the team for review.

2 Likes

I’ve got this reply few times,here and Reddit we need solutions. Instead Bragging on social media how great the browser is try to fix these issues please.

@Sakalabujhan ever stop to consider there are millions of users and that perhaps the problem is only with you or a very small niche group of people? Speaking of millions, there are also millions of lines of code to sort through and it can be incredibly tough to figure out a problem. Often solutions get quicker fixes when there are lots of people having the same issue or the problem is easily replicated. Otherwise it can take a long time.

Presently all you have said is it randomly happens. That’s not a lot of details or help overall. And I’m not seeing a lot of similar reports. The closest I’m getting would be some of the ones below, but they seem like they don’t quite match up with your issue. And one was resolved by changing their browser theme.

That said, @Mattches and @steeven wanted to tag you both in, especially since both of you had been handling prior crash report here. I merged new topic from OP with old one. So it seems Steeven, Mattches, and Evan123 have all touched this issue shared by Sakalabujhan.

Not sure if any of you in particular is juggling. Anyway, also have the linked issues which may or may not be related, but there to check and possibly give any updates if any.

Thanks.