I have Brave installed on 3 differnt versions of Linux for the Raspberry Pi. I also have both the Rpi 4 and 5
Raspberry Pi OS.
MX Linux ( Based on the RP OS with tweaks)
Ubuntu 24.04LTS
The first 2 use the Debian arm64 link from Brave for the installation source and run on the Rpi4 perfectly but crash on a Pi5.
The snap package used by Ubuntu runs perfectly on both SBCs
I’ll jump in saying I’m having the same issue. I have my Brave package on hold at Version 1.71.123 Chromium: 130.0.6723.116 (Official Build) (64-bit) since that is the last version that works for me.
I’ve re-installed Brave, wiped all Brave data, and whatever else I can think of, but anything newer than 1.71.123 crashes within minutes of loading.
This long-running “Aw Snap” issue exists for Raspberry Pi5 BB users.
It appears that there are NO Brave developers for the Raspberry PI OS that are watching this forum or could care less? When on hold at version 1.71.123 Brave now suggests we need to update it. Of course, I will NOT do that UNTIL someone comes up with a fix.
It would be very helpful if we could get crash reports from a version of the browser that exhibits the issue. I’ve reached out to some devs about this as well.
1 Like
I thought crash reports were already uploaded. I can wipe, update and upload whatever log you need… Just need to know what you are looking for.
@Olympics1639 if you are able to snag the crash report ID(s) for those crashes to me here we can look them up on our end to help root out the cause.
- Closed Brave
- Removed ~/.config/BraveSoftware
- Updated Brave via apt package manager
- Googled how to access Brave crashes
- Opened settings
- Opened Brave Community and searched for this thread
- Saw multiple crashes, made sure each was uploaded and copied information from brave://crashes
Let me know if this is enough or if you need something else.
Crash from Tuesday 14 January 2025 at 16:38:42
Status: Upload requested by user
Local crash context: a33fb8cd-b7ad-4964-b25d-1a473e889347
Crash from Tuesday 14 January 2025 at 16:37:52
Status: Uploaded
Uploaded crash report ID: 01fc1800-92d4-340d-0000-000000000000
Upload time: Tuesday 14 January 2025 at 16:38:44
Local crash context: d9314c04-a725-4b0b-a027-aaa1a037c306
Crash from Tuesday 14 January 2025 at 16:37:33
Status: Uploaded
Uploaded crash report ID: fefb1800-92d4-340d-0000-000000000000
Upload time: Tuesday 14 January 2025 at 16:38:43
Local crash context: bfc54101-15b6-47ce-a1fe-cae85af3938e
Crash from Tuesday 14 January 2025 at 16:36:55
Status: Uploaded
Uploaded crash report ID: fbfb1800-92d4-340d-0000-000000000000
Upload time: Tuesday 14 January 2025 at 16:38:43
Local crash context: 2c2a56c5-73ba-4a9f-bb74-ef1d0cb43bf2
Crash from Tuesday 14 January 2025 at 16:36:11
Status: Uploaded
Uploaded crash report ID: a0fa1800-92d4-340d-0000-000000000000
Upload time: Tuesday 14 January 2025 at 16:36:11
Local crash context: 58e685f2-0455-44c3-8941-4a2db9960992
Crash from Tuesday 14 January 2025 at 16:35:48
Status: Uploaded
Uploaded crash report ID: 0dfb1800-92d4-340d-0000-000000000000
Upload time: Tuesday 14 January 2025 at 16:36:56
Local crash context: 260b1b9c-0109-4d6c-8f90-36ce0a3a3456
Crash from Tuesday 14 January 2025 at 16:35:16
Status: Uploaded
Uploaded crash report ID: 0afb1800-92d4-340d-0000-000000000000
Upload time: Tuesday 14 January 2025 at 16:36:56
Local crash context: 38656219-2b1c-4175-8b0f-99e65d38f286
@Olympics1639 no that’s perfect, thank you. Will reply back here when I hear back from the team.
The team has identified this as an upstream issue — unfortunately it looks like we’ll have to wait for the upstream fix as well:
https://issues.chromium.org/issues/378017037
Wow … great to know someone from Browser support will look at this. I am a Linux rooky so I do not know how to generate crash reports however it looks like Olympics1639 will do that. I now have hope this will get fixed.
Thank you @Mattches. I’ll keep watching this issue. If Brave devs need more logs from another build, I’m happy to generate those.
Great to know you are working on a fix, but I believe the current version of Chromium on the Pi5 system does NOT croak and works well.
Thanks for looking into this and thanks to the person who sent you those crash reports.
@HalAdam Can you do me a favor and upgrade your Brave browser to the latest and try launching Brave from the command line using the following?
brave-browser --js-flags="--nodecommit_pooled_pages"
If you need to go back to the last working version, you can do the following:
sudo apt install brave-browser=1.71.123
sudo apt-mark hold brave-browser
I’m typing out this reply on “Version 1.73.105 Chromium: 131.0.6778.265 (Official Build) (64-bit)” with the flags set above. So far so good, but I have limited runtime.
Edit: I’ve been browsing for 2 hours without crashes. This may not fix the issue, but as a workaround, it seems to lessen the frequency greatly.
1 Like
Brave Version 1.74.50 Chromium: 132.0.6834.111 (Official Build) (64-bit) has the same challenge. The challenge is known on the Raspberry Pi forum, however the ping pong match says the Brave team need to investigate.
It’s definitely related to the Chrome issue linked above (https://issues.chromium.org/issues/378017037).
I’ve been running lastest version of Brave on my Raspberry Pi 5 for 10 days and the difference is drastic. I go from tabs crashing every 60 seconds to maybe 1 tab crash every couple days… Which is the same frequency I see on older versions of Brave.
I’ve modified my Brave desktop shortcut to include the run flag I listed above, so the workaround is seamless on my end.
Edit: Source for my work around is listed here: https://issues.chromium.org/issues/378017037#comment28
1 Like
Thank you for the workaround:
Aw snap error code 5 after install of Brave version 1.73.89 on Raspberry Pi5 - #34 by Olympics1639
Aw snap error code 5 after install of Brave version 1.73.89 on Raspberry Pi5 - #36 by Olympics1639
(And, I am bumping this page, to keep it alive - because the issue has not been resolved by Chromium.)
1 Like
I did an Raspberry PI update today which included updates to Chromium and Brave (took a risk) and after the update and reboot there was not longer ANY Snap error from the Brave Browser so I consider my original reporting on this issue closed.
2 Likes
+1. I updated Brave and removed my “–js-flags=” workaround. Brave has been running without crashes.
GREAT and THANKS to the person(s) who fixed this!