Package Details: brave-nightly-bin 1.67.32-1

Git Clone URL: https://aur.archlinux.org/brave-nightly-bin.git (read-only, click to copy)
Package Base: brave-nightly-bin
Description: Web browser that blocks ads and trackers by default (nightly binary release).
Upstream URL: https://brave.com/download-nightly
Licenses: MPL2
Provides: brave-nightly-bin, brave-nightly-browser
Submitter: gregbunk
Maintainer: gregbunk
Last Packager: gregbunk
Votes: 25
Popularity: 0.094896
First Submitted: 2019-03-28 14:18 (UTC)
Last Updated: 2024-04-23 11:26 (UTC)

Dependencies (9)

Required by (0)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

gregbunk commented on 2022-06-06 20:56 (UTC)

Sorry about that. Should be fixed now.

Khaithang commented on 2022-06-06 20:52 (UTC)

sha512sum checks fails, i am getting:

04eccdc6c17b22b4a5faedd5334e655de7e76f7003554771837489bb3479768a25d60170595d3b1f2377b503ee7fb67c5f2ef36c3ad2a058dc285805bb7c4b35

and not 06f3503f4166c9d5f750dcf809247bc9990b9d42b99227ce15674381d9756ef61ffd1acf95733fce7bcdaa8baddc84498d7f5e96bd09d1811dd3d467b7b9eec9

as given in PKGBUILD for the deb package.

Archanfel80HUN commented on 2022-04-29 07:47 (UTC) (edited on 2022-04-29 14:54 (UTC) by Archanfel80HUN)

Im trying to figure out what exactly triggered the memory leak. I cant reproduce the issue exactly, sometimes its just happens if i use the nightly build. With the standard build its not happened thats for sure.

UPDATE: i think i found it. Something in the .config/BraveSoftware folder messed up. I did delete everything except the Default folder which contained the profile, purged the cache and the temp files. It seems this fixed the issue. I did rolled this folder since many years now and tgz the whole before any OS reinstall, so something probably messed up in there. I dont want to celebrate too early but it seems the issue is gone now.

gregbunk commented on 2022-04-28 14:20 (UTC)

I use KDE as well - and haven't seen this.

Archanfel80HUN commented on 2022-04-28 14:14 (UTC)

It seems only affect KDE plasma. Somehow interfered with kde5d and not closing the unused socket connections. Eventually even if i kill all of the brave process the kde5d remains consuming all the available sockets. It did not occured with other DE like xfce or i3, but it also not occured with the non nightly version of brave, not even in KDE. So the problem is with the nightly and with KDE specifically. I will report this issue for sure but i use the standard version for now because my main DE is KDE.

gregbunk commented on 2022-04-28 12:57 (UTC)

I haven't seen that, Archanfel80HUN. That does sound frustrating.

Please report that to Brave directly - this is simply a repackaged version of what they produce.

Archanfel80HUN commented on 2022-04-28 11:35 (UTC)

In the latest 2-3 updates i noticed a nasty bug. Its have a memory leak which is consumed all the available Xsocket connection. Once the maximum connection of Xorg sockets depleted nothing starts anymore and the whole system become unresponsive. The log files full of this: cannot open display: :0.0 Maximum number of clients reached

According to xrestop brave eats 190+ connection and eventually the default 256 limit reached. Revert back to the non nightly version the problem is gone.

gregbunk commented on 2021-10-21 20:18 (UTC)

Not seeing any glitches here, but am seeing the (annoying) warning. It appears that brave is setting that itself, when it starts the renderer processes.

I'll keep poking around.

DelightfulFlower commented on 2021-10-21 20:06 (UTC) (edited on 2021-10-21 20:06 (UTC) by DelightfulFlower)

What is going on with the latest version (1.33.25-2) since I get a warning when opening the browser:

You are using an unsupported command-line flag: --translate-security-origin=https://translate.brave.com. Stability and security will suffer."

Stability definitely suffered since the browser has weird glitches now.

wknapik commented on 2021-10-21 17:09 (UTC)

Thanks gregbunk!