Brave crashes probable solution

I think it has been fixed! I haven’t changed anything, but haven’t had it crash once on Rome in the past 5 days. I was affected significantly by it too. It looks like the Brave team might have rolled out a fix, even if Chromium haven’t (extension page still crashes on that).

How are others going who were significantly affected?

I still have crashes.

3 Likes

This issue is proving very hard to address. I wonder if collecting and parsing all sorts of data from users who do and do not suffer this issue would help? Maybe even feeding all the data into a LLM AI?

I like the idea of contributing data. I’m someone who doesn’t have the crashing issue at all. I also just did a fresh reinstall of ROME on both my desktop and laptop to help test out an install script that I’ve been working on. Separate from that install script, I always install Brave from the Welcome menu as one of the first things I do with a fresh install. I’m curious is those who have the crashing issue also installed Brave from the Welcome menu, or if they used the CLI. I’m not sure why there would be a difference, but it would be interesting if that were the case.

Yes the default chromium crashes. Especially when trying to open extensions. Going to a page to install them also has errors or in case of Chrome store, says they cannot be installed. I’ve tried removing the package and installing one from flatpak and same issue occurs but not in Brave. It doesn’t bother me because I don’t use it sense ublock origin is no match for the Brave shields anyways. Putting up with clicking a crypto icon to hide it is a small price to pay. Some distros have announced they are only shipping Brave now anyways sense the Mozilla/Firefox scandal. Yeah we got a sneak peak into that mess. Firefox can’t be trusted anymore. Some apps and app images do rely on Chromium to use pywebview to display instead of using other browsers. So I think of it more internal use and no so much a personal browser choice. As for those using Brave Browser that crashes, one person outside of this forum noted that disabling the extension for Plasma desktop integration fixes this issue. However I have not tested this myself sense I do not have the issue.

2 Likes

I wanted to reply here as I’ve been experiencing the issue with Brave and I had a chance to look at it this morning. I also took a look at Chromium and Falkon to see if issues were similar as these are both related browsers offered here. I didn’t have time for a deep dive, so the reply will reflect where I am now. First, from what I see all three browsers crashed for completely different reasons, at least in my case. I will share what I found on Brave and Chromium here and be quick …

Brave: I’ve been observing similar behavior to that of others on this thread, so I started from the command line as such: brave-browser --enable-crash-reporter --enable-logging --v=137. My plan was to see if there was anything in the logs to lead me further. The logs yielded only KWallet-related errors. I don’t use KWallet, or any wallet, so I lazily clicked cancel when starting Brave for the very first time. I attempted to disable to the KWallet subsystem with that setting, but the errors were still present. I then re-enabled KWallet and unchecked the Use KWallet for the Secret Service interface setting. This took away the KWallet errors with Brave on startup and I haven’t had a crash since.

Chromium: I had also started the browser in a similar way with a similar thought process in mind as such… ‘chromium --enable-crash-reporter --enable-logging --v=137’… Generally, I haven’t observed any instability or crashing with this browser at all. However, when I attempt to click Manage Extensions as others have mentioned issues with, the browser does in fact crash. At first glance, the crashes seem to be related to the way that this feature has been “degoogled” and then the subsequent Chromium handling thereafter. Please see a snip of the log here…

[6494:6510:0821/102424.375501:ERROR:url_request.cc(649)] Block URL in URLRequest: https://chrome.9oo91e.qjz9zk/webstore?hl=en
[6494:6510:0821/102424.376259:ERROR:trk_protocol_handler.cc(17)] Blocked URL in TrkProtocolHandler: trk:https://chrome.9oo91e.qjz9zk/webstore?hl=en
Fontconfig error: Cannot load default config file: No such file: (null)

Also, see the dig results for the domain here:

dig 9oo91e.qjz9zk

; <<>> DiG 9.21.0 <<>> 9oo91e.qjz9zk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37088
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;9oo91e.qjz9zk. IN A

;; AUTHORITY SECTION:
. 7168 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025082100 1800 900 604800 86400

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Aug 21 11:32:15 EDT 2025
;; MSG SIZE rcvd: 117

Since the domain doesn’t exist, the Manage Extensions functionality could never work in Chromium. The poster who found and shared an alternative way of installing the extensions would seem to have the right solution for those that require the use of extensions with Chromium. Finally, I actually don’t even like so many things about Brave, so I might just install some extensions to this Chromium and see where it goes.

At your suggestion, I turned off the extension for Plasma Desktop Integration and I have not managed to get Brave to crash in 3 days.

Can anyone else verify?

1 Like

I only use Brave on one system running Rock6.0. Brave is open for days to weeks at a time with no crashes, but I always disable the plasma browser integration.

I’ve never had Brave crash, and I’ve had Plasma Integration on all the time.

Still no crash with Plasma Desktop Integration removed. That’s 5 days now.

1 Like

After 7 days with no crashes. Brave just crashed with Plasma Desktop Integration disabled.

I install Brave via script, and I don’t have crashing problems:

## Enable Brave
sudo wget https://brave-browser-rpm-release.s3.brave.com/brave-browser.repo -O /etc/yum.repos.d/brave-browser.repo
sudo rpm --import https://brave-browser-rpm-release.s3.brave.com/brave-core.asc
sudo dnf -y install brave-browser

Still crashes but not so often as before. :slight_smile:

It’s crazy but I can live with that

For me It is also true, 3 crash in a row couple minutes ago. I haven’t have Plasma Integration enabled even once. So it is not a cause of my crashes.

1 Like

Just to follow up, I even tested it on Fedora and it crashes there too. Only on this PC and the other one has not crashed once. I still don’t get it.

1 Like

I’ve had it crash once now, in the several months that I’ve been using OML.
It was on the first use of it after a reboot.
I’d say I’ve rebooted my system about 1-2 times a month since I installed OML.

1 Like

Yes, that is when we all see it.

Like you, I used to only reboot when system upgrades required it, but I now power down nightly, so I see it a lot.

1 Like

I use the flatpak and I don’t think I’ve ever had brave crash

I’ve had random crashes but not frequent fortunately.

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