Description of the issue:
The first time Brave is opened, everything is fine. All subsequent launches while having the first window still open (necessary!), gives a segmentation fault, even though the new window opens fine.
Steps to Reproduce (add as many as necessary):
$ brave
$ brave while the first window is still open.
Actual Result:
[3878:3878:0412/075149.391477:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
Opening in existing browser session.
--2019-04-12 07:51:49-- https://laptop-updates.brave.com/1/bc-crashes
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving laptop-updates.brave.com (laptop-updates.brave.com)... 151.101.165.7
Connecting to laptop-updates.brave.com (laptop-updates.brave.com)|151.101.165.7|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16 [text/html]
Saving to: ‘/dev/fd/4’
/dev/fd/4 0%[ ] 0 --.-KB/s
Crash dump id: /dev/fd/4 100%[=============>] 16 --.-KB/s in 0s a6088c30a3c579d1
2019-04-12 07:51:50 (6.22 MB/s) - ‘/dev/fd/4’ saved [16/16]
[1] 3845 segmentation fault (core dumped) brave
Expected result:
I expect that it doesn’t return a segmentation fault.
Reproduces how often:
Every time.
Operating System and Brave Version
Linux 5.0.3
Brave version 0.62.51, Chromium: 73.0.3683.103
Additional Information:
I don’t experience this issue on plain Chromium 73.0.3683.103 (same version as above).
Same here, Fedora 29 & i3. Error message in my case:
[10264:10264:0416/155921.628668:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
Segmentation fault (core dumped)
I’ve been dealing with this for a few weeks. At first it wasn’t clear what was going on at all because it presented itself symptom wise as opening chrome every time I clicked to open a link from an external program.
It ALSO opens the link successfully in a new tab in Brave.
Happening on 3 of my Ubuntu 18.04 systems. Same log as already posted to thread.