Crashes after ≈5 seconds

[Kaympe20]

Description

Steps to Reproduce

1. Download app from flathub
2. Open
3. Crash

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

• 1.60.114
• Linux (Flatpak)

Version/Channel Information:

• Can you reproduce this issue with the current release?
  N/A
• Can you reproduce this issue with the beta channel?
  N/A
• Can you reproduce this issue with the nightly channel?
  N/A

Other Additional Information:

• Is the issue reproducible on the latest version of Chrome?
  No

[rebron]

cc: @wknapik

[wknapik]

@Champe20 issues with the flatpak package should be logged at https://github.com/flathub/com.brave.Browser/issues, as this is not an official package.

There are currently several open (likely duplicate) issues for crashes on startup on arm64 affecting the non-flatpak variant of the browser - #34122, #34120, #34118. If you're on arm64, this could the root cause.

The above crashes are being worked on.

If you share what the browser prints when started from a terminal, or if you have any uploaded crash IDs, that would help. The crash IDs can be found at brave://crashes once Automatically send diagnostic reports is enabled in brave://settings.

[wknapik]

@Champe20 does the same thing happen with the non-flatpak package? Installation instructions are described at brave.com/linux.

You can also try launching the browser with a fresh profile, by passing --user-data-dir="$(mktemp -d)" on the command line.

[aneeshlingala]

This also happens with the non-flatpak package.

[wknapik]

I think it's pretty safe to assume this issue has the same underlying cause as some of the issues reported in the non-flatpak package. Given how many duplicate issues there are now and that we're not going to do anything specifically for flatpak, I'm going to close this one. Please follow the other issues to track progress:

• confirmed arm64
  • Brave crashes on various Linux ARM64 at launch #34120
  • Brave crashes on Ubuntu ARM64 (Asahi Ubuntu) #34118
  • Segmentation fault on startup - brave ubuntu 22.04 arm64 #34106
  • Segfault at startup on arm linux #33596
• unspecified architecture
  • New Release Crash - Ubuntu 22.04 #33619
• confirmed x64
  • Brave doesn't opening: ERROR:elf_dynamic_array_reader.h(64)] tag not found #24380
  • Brave crashes on Ubuntu 22.04 LTS after ERROR:elf_dynamic_array_reader.h(64)] tag not found #34122
  • this issue

[Kaympe20]

@wknapik I am on x86_64

[wknapik]

@Champe20 thanks. If you're able to share crash IDs, like I mentioned earlier, that would be helpful.

I'll reopen for now, since the other issues are mostly on arm64.

[Kaympe20]

@wknapik I have been able to replicate the issue on Fedora based immutable distros such as Fedora Kinoite and uBlue, however I could not do the same on non-immutable distros such as Fedora KDE. I will boot up a VM to try reproduction. How can I find the crash logs?

[wknapik]

How can I find the crash logs.

The crash IDs can be found at brave://crashes once Automatically send diagnostic reports is enabled in brave://settings.

At brave://crashes you'd have to click Send now on a crash and then share the string that appears after Uploaded Crash Report ID:.

If the browser crashes with a delay, hopefully you'd be able to do all that in a few attempts.

[Kaympe20]

@mkarolin I don't believe I can do that in the time it takes until it crashes. Is there a file path I can find it at?

[mkarolin]

@Champe20, crash reports are typically stored under your profile directory. For example, on Ubuntu it would be ~/.config/BraveSoftware/Brave-Browser/Crash\ Reports/. Please, check the folders there for .dmp files.

[wknapik]

@Champe20 is this still happening on the latest native (not flatpak/snap) browser version?

[Kaympe20]

@wknapik I have not been able to reproduce the issue, flatpak or otherwise since November 28.