brave-browser: Segmentation fault when launching a second window via terminal
Description
Segmentation fault when launching a second window via terminal.
Steps to Reproduce
- Launch brave from terminal
- Open a new terminal window and launch a second window
- Console logs segmentation fault and exits but the second browser window is still opened
Actual result:
Release (Manjaro): No crash dump ID generated for release on Ubuntu
User namespaces are not detected as enabled on your system, brave will run with the sandbox disabled
Opening in existing browser session.
[106257:106257:0417/082009.710955:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
Segmentation fault (core dumped)
Beta: Crash Dump
brave-browser-beta
--2019-04-17 08:46:19-- https://laptop-updates.brave.com/1/bc-crashes
Resolving laptop-updates.brave.com (laptop-updates.brave.com)... 151.101.21.7
Connecting to laptop-updates.brave.com (laptop-updates.brave.com)|151.101.21.7|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16 [text/html]
Saving to: ‘/dev/fd/4’
0K
Crash dump id: 5ad446cca388b589
100% 2.18M=0s
2019-04-17 08:46:19 (2.18 MB/s) - ‘/dev/fd/4’ saved [16/16]
Segmentation fault (core dumped)
Dev: Crash dump
brave-browser-dev
--2019-04-17 08:47:01-- https://laptop-updates.brave.com/1/bc-crashes
Resolving laptop-updates.brave.com (laptop-updates.brave.com)... 151.101.21.7
Connecting to laptop-updates.brave.com (laptop-updates.brave.com)|151.101.21.7|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16 [text/html]
Saving to: ‘/dev/fd/4’
0K
Crash dump id: 16e3a3a988197e80
100% 2.06M=0s
2019-04-17 08:47:01 (2.06 MB/s) - ‘/dev/fd/4’ saved [16/16]
Segmentation fault (core dumped)
Expected result:
No segmentation fault to be shown when launching a second window via terminal
Reproduces how often:
Easy
Brave version (brave://version info)
| Brave | 0.62.51 Chromium: 73.0.3683.103 (Official Build) (64-bit) |
|---|---|
| Revision | e82a658d8159cabbd4938c1660f9bb00b4a82a23-refs/branch-heads/3683@{#902} |
| OS | Linux |
Reproducible on current release:
- Does it reproduce on brave-browser dev/beta builds? Yes
Website problems only:
- Does the issue resolve itself when disabling Brave Shields? N/A
- Is the issue reproducible on the latest version of Chrome? N/A
Additional Information
Issue originally reported on community. https://community.brave.com/t/second-launch-gives-segmentation-fault/53664/5
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 18
- Comments: 22 (9 by maintainers)
Commits related to this issue
- xfce4-exo: update to 0.12.6 0.12.6 ====== - Bug Fixes: - Add trailing ";" to mimeapps.list (Xfce #15087) - Clear bad entries from mimeapps.list (Xfce #15046, #15238) - Synchronize default appli... — committed to NetBSD/pkgsrc by dhgutteridge 5 years ago
- [update to 0.12.6] - If the error can be safely ignored, the user is able to dismiss 0.12.6 ====== - Bug Fixes: - Add trailing ";" to mimeapps.list (Xfce #15087) - Clear bad entries from mimeapps... — committed to clearlinux-pkgs/exo by fenrus75 5 years ago
- Work around startup crashes on Linux (brave/brave-browser#4142) — committed to brave/brave-core by fmarier 5 years ago
- Fix xdg-open brave issue https://github.com/brave/brave-browser/issues/4142#issuecomment-504742158 — committed to artemave/dotfiles by artemave 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) — committed to brave/brave-core by fmarier 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) — committed to brave/brave-core by fmarier 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) The `brave` binary returns a non-zero error code and that causes the wrapper to return a non-zero error code too. Since it's not possib... — committed to brave/brave-core by fmarier 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) The `brave` binary returns a non-zero error code and that causes the wrapper to return a non-zero error code too. Since it's not possib... — committed to brave/brave-core by fmarier 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) The `brave` binary returns a non-zero error code and that causes the wrapper to return a non-zero error code too. Since it's not possib... — committed to brave/brave-core by fmarier 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) The `brave` binary returns a non-zero error code and that causes the wrapper to return a non-zero error code too. Since it's not possib... — committed to brave/brave-core by fmarier 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) The `brave` binary returns a non-zero error code and that causes the wrapper to return a non-zero error code too. Since it's not possib... — committed to brave/brave-core by fmarier 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) The `brave` binary returns a non-zero error code and that causes the wrapper to return a non-zero error code too. Since it's not possib... — committed to brave/brave-core by fmarier 5 years ago
- Hack wrapper to work around segfault (brave/brave-browser#4142) The `brave` binary returns a non-zero error code and that causes the wrapper to return a non-zero error code too. Since it's not possib... — committed to brave/brave-core by fmarier 5 years ago
Workaround to make
xdg-openwork as expected is to make sure the executable thatbrave.desktopis calling always returns0exit code, for example make it execute a wrapper script like this one:I have a similar problem, opening external links opens 3 new tabs with the same url. Opening links directly from the terminal results in segmentation fault, but it only opens 1 new tab.
I’m happy the work around is released, but fear that as it no longer bites people, the motivation to fix the root cause will atrophy 😕
Clicking on links in the desktop brings that annoying popup on Xubuntu too. Here is a strace, if it may help: https://gist.githubusercontent.com/teresaejunior/e5c0f6b51f2d93e2ffe4fda1953d5b4d/raw/2d5d665b7f72b2e6421627ff6e8609d2b37144a4/strace
In that case, you’re seeing a different issue on that machine. This is most likely #7581 (inherited from the last Chromium merge).
The work-around has been merged to the Beta (0.70.x) and Dev (0.71.x) branches too.
I’m going to take a look at this, it’s a pretty bad papercut.