Browser crashes when opening a bookmark folder

Browser Support Desktop Support
, ,
1

Description of the issue:
Since the last update I can’t open a bookmark folder that has 24 or more bookmarks in it without the browser crashing, it worked without issues before the last update. Opening a bookmark folder with 17 or fewer bookmarks still works normally. If I use the hamburger menu and go to “Bookmarks and lists“ and then click/open the bookmark folder then it lists all bookmarks without crashing, it’s only for folders on the bookmark menu.

I tried creating a new folder to see if it only happened with old folders but it crashed as well if it had 24 or more bookmarks. Restarting the computer also did not help.

How can this issue be reproduced?

  1. Open/click on a bookmark folder with 24 or more bookmarks

Expected result: Opens normally without crashing like it did before the last update

Brave Version( check About Brave): Brave 1.82.166

Additional Information:

2

This is happening to me as well, same symptoms. I’m on Debian 13.

Brave 1.82.166 (Official Build) (64-bit)

A tiny bit more info, if I run it from the command line, this is the error:

/usr/bin/brave-browser: line 39: 8713 Illegal instruction “$HERE/brave” “$@”

(not very helpful I know, but that’s all there is)

3

This might be related to https://github.com/brave/brave-browser/issues/49160 , or at least if I run via the command line with the brave-browser --ozone-platform=x11 flag it’s no longer crashing in the same way.

4

Can confirm the same issue on Arch using Wayland and KDE Plasma, running Brave 1.82.166 (Official Build) (64-bit).

The --ozone-platform=x11 workaround also works for me.
Not much, but hopefully confirmation on a different distro is worth something.

5

@Mattches

The OP issue, and more info.

And a workaround for the moment.

6

Seems to be fixed on Brave 1.83.109 (Official Build) (64-bit), via the AUR for Arch.

7

Adding the --ozone-platform=x11 flag did also fix it for me.

After the latest update I removed flag and now works normally, so the issue is now fixed on my end too.