Brave browser launches but crashes immediately with segmentation fault

jayadevanraja commented 1 year ago

Description

When launching Brave browser from the terminal using either /usr/bin/brave-browser
or
/snap/bin/brave

Brave launches but immediately crashes with a segmentation fault error:

/usr/bin/brave-browser --incognito
[19923:19923:0720/153022.082073:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.  
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

/usr/bin/brave-browser: line 48: 19923 Segmentation fault      (core dumped) "$HERE/brave" "$@"

I have tried:

Reinstalling Brave via both the .deb and Snap packages
Deleting and recreating the Brave cache
Updating all Ubuntu packages

But the issue persists after each attempt.

System Info:

Ubuntu 20.04
Brave browser 1.56.9

Steps to Reproduce

In terminal, type "/usr/bin/brave-browser --incognito" or /snap/bin/brave --incognito, as the case may be.
See the error messages

Actual result:

Segmentation Fault

Expected result:

Browser opens in incognito mode, as expected

Reproduces how often:

After today's (2023-07-20) update, Brave never opens in incognito mode.

Brave version (brave://version info)

Version/Channel Information:

Brave browser 1.56.9
Can you reproduce this issue with the current release? Yes
Can you reproduce this issue with the beta channel? Not Tried
Can you reproduce this issue with the nightly channel? Not Tried

Other Additional Information:

Does the issue resolve itself when disabling Brave Shields? Never Tried
Does the issue resolve itself when disabling Brave Rewards? Never Tried
Is the issue reproducible on the latest version of Chrome? Yes. Google Chrome crashes at "google-chrome --incognito". Chromium is in "Version 114.0.5735.198 (Official Build) snap (64-bit)", and it does not crash.

Miscellaneous Information:

Brave started crashing only after current update. I believe this to be the same case with Google Chrome. Chromium "Version 114.0.5735.198 (Official Build) snap (64-bit)" does not crash, and that is the latest stable build available now for Ubuntu GNU/Linux system. So, I do not have access to version 117.0.5900.0 of Chromium to try it.

wknapik commented 1 year ago

Not seeing this on hardened Arch Linux on any browser channel, nor snap

@jayadevanraja is this still an issue with the latest release?

nicolasfiel commented 1 year ago

Hi, I have the same crash and error message since this update too. Brave: Version 1.57.47 Chromium: 116.0.5845.96 (Build officiel) (64 bits) OS: Ubuntu 18.04.6 LTS (I know, old one) The only way to open a new page in incognito mode without crashing is from a non-incognito page. Direct launch of brave in incognito mode (from the menu or in command-line) crashes systematically. Opening a new incognito page from an open incognito page crashes all brave processes.

wknapik commented 1 year ago

@nicolasfiel could you enable crash reporting and share crash ids from brave://crashes?

nicolasfiel commented 1 year ago

I forgot I already had it enabled in fact, here are my 5 latest crash reports: ID du rapport d'erreur importé : | 37e00100-0e1b-930a-0000-000000000000 Heure de l'importation : | jeudi 17 août 2023 à 20:14:11

ID du rapport d'erreur importé : | f8840000-0e1b-930a-0000-000000000000 Heure de l'importation : | jeudi 17 août 2023 à 00:18:44

ID du rapport d'erreur importé : | c1390000-0e1b-930a-0000-000000000000 Heure de l'importation : | mercredi 16 août 2023 à 20:10:15

ID du rapport d'erreur importé : | f95f0800-b0e3-890a-0000-000000000000 Heure de l'importation : | mardi 15 août 2023 à 09:55:50

ID du rapport d'erreur importé : | 0df60100-b0e3-890a-0000-000000000000 Heure de l'importation : | jeudi 10 août 2023 à 22:37:00

jayadevanraja commented 1 year ago

@wknapik I am so sorry for the late reply.

Yes, the problem is still there, as seen from this terminal session:

appu@appu-LIFEBOOK-A555:~$ google-chrome --incognito
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

[271314:271314:0819/222646.834519:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.portal.Error.NotFound: Requested setting not found
Segmentation fault (core dumped)
appu@appu-LIFEBOOK-A555:~$ brave --incognito

Command 'brave' not found, but can be installed with:

sudo snap install brave

appu@appu-LIFEBOOK-A555:~$ brave-browser --incognito
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

[271616:271616:0819/222718.715329:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
/usr/bin/brave-browser: line 48: 271616 Segmentation fault      (core dumped) "$HERE/brave" "$@"
appu@appu-LIFEBOOK-A555:~$
appu@appu-LIFEBOOK-A555:~$ chromium-browser --incognito

Command 'chromium-browser' not found, but can be installed with:

sudo apt install chromium-browser

appu@appu-LIFEBOOK-A555:~$ chromium --incognito
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored.
Gtk-Message: 22:32:55.958: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
[272492:272492:0819/223257.357895:ERROR:chrome_browser_cloud_management_controller.cc(163)] Cloud management controller initialization aborted as CBCM is not enabled.
[272492:272492:0819/223301.749524:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.portal.Error.NotFound: Requested setting not found
[0819/223302.520169:ERROR:ptracer.cc(567)] ptrace: Input/output error (5)
[0819/223302.640242:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0819/223302.684545:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Segmentation fault (core dumped)
appu@appu-LIFEBOOK-A555:~$

This problem is existent for Chrome and Brave. Chromium also has developed this issue now. I now have Chromium version "Version 116.0.5845.96 (Official Build) snap (64-bit)".

If I should report this elsewhere too, I shall do that. The problem is there only for chromium-based browsers, and not Firefox.

wknapik commented 1 year ago

Thanks @jayadevanraja. Could you also share some crash ids?

jayadevanraja commented 1 year ago

@wknapik I don't know how to do that. If this is what you mean, this is what I got in brave://crashes/

Show developer details
Crash from Saturday, 19 August 2023 at 22:27:19
Status: Not uploaded
Local crash context:    e36fbec1-4ac1-4c29-8ed7-e960d2682d8a

If this is not what you meant, please say how to find the crash IDs.

wknapik commented 1 year ago

@jayadevanraja there should be a link/button to press per crash to send the report. Once the upload is done, the crash ID will be shown labelled Uploaded Crash Report ID.

ivan-aksamentov commented 1 year ago

Same issue for me. Also happens in Chromium.

Could you please relay this to chromium folks and/or teach me how to do it?

Crash from Sunday, August 20, 2023 at 2:27:52 AM Status: Uploaded Uploaded Crash Report ID: ce6b0500-0e1b-930a-0000-000000000000 Local Crash Context: 8d0349f1-ca34-491a-9c29-88c38fbef9f2 Upload Time: Sunday, August 20, 2023 at 2:29:03 AM

Brave Version: 1.57.47 Chromium: 116.0.5845.96 Operating System: Ubuntu 20.04 (Linux 5.8.0-45-generic)

URL (if applicable) where crash occurred: on startup when adding --incognito flag

Can you reproduce this crash?

What steps will reproduce this crash? (If it's not reproducible, what were you doing just before the crash?)

Install Brave on Ubuntu 20.04 from official Brave repos
Open terminal and run brave-browser --incognito

Observe window shows for a split second then disappers. Observe the following console output:

MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

[3068704:3068704:0820/022751.965065:ERROR:chrome_browser_cloud_management_controller.cc(163)] Cloud management controller initialization aborted as CBCM is not enabled.
/usr/bin/brave-browser: line 48: 3068704 Segmentation fault      "$HERE/brave" "$@"
[3068770:3068783:0820/022752.202137:ERROR:ssl_client_socket_impl.cc(968)] handshake failed; returned -1, SSL error code 1, net_error -3

This only happens when starting Brave/Chromium in incognito mode. Opening it in normal mode works fine. Opening new incognito window from the menu of the normal window works fine.

In noticed this happening in Chromium since version 113-115 or so. I use Chromium from Debian repos.

The only version of Chromium I could find and install that does not crash is 112:

apt-get install chromium=112.0.5615.138-1\~deb11u1 chromium-common=112.0.5615.138-1\~deb11u1 chromium-driver=112.0.5615.138-1\~deb11u1 libwebpmux3=0.6.1-2.1

(when downgrading, explicit version of libwebpmux3 is required, because otherwise apt-get complains its incompatible)

The other versions of chromium I tried: 115, 116 - all crash. I could not find versions 113 and 114 to try.

The earliest currently available version of brave in the apt repo 1.51.118 still crashes and afew of the randomly picked versions between this and the latest version 1.57.47 all crash too.

DO NOT CHANGE BELOW THIS LINE Crash ID: crash/ce6b0500-0e1b-930a-0000-000000000000

jayadevanraja commented 1 year ago

@wknapik If I use --incognito in the GUI menu, the browsers (Brave, Chrome, and now Chromium also) do not show any crash reporting dialogue box for me. The icon comes in the Unity sidebar (I use Unity Desktop) and then it vanishes. If I use it in the terminal, the reason is shown as segmentation fault.

wknapik commented 1 year ago

@jayadevanraja I meant that after the browser crashes, you can start it not in incognito mode, go to brave://crashes and there, you should see the list of recent crashes. If any of them say Not uploaded (like you mentioned in your previous comment), then you'd have to press a button/link for each crash to upload the crash report. Once the upload is done, the crash should have an Uploaded Crash Report ID displayed - those are the IDs we're looking for.

brave / brave-browser