[SOLVED] Aw, Snap! SIGSEGV

Problems with packages? Post here, using [tags] of the package name.

[SOLVED] Aw, Snap! SIGSEGV

Postby Lander1979 » Thu Apr 30, 2020 4:35 am

Since updating yesterday, my Chromium browser crashes with Aw, Snap! SIGSEGV in the browser tab.

Chromium Version 81.0.4044.129 (Official Build) Arch Linux ARM (32-bit)

Running Chromium via Terminal gives the following output;
$this->bbcode_second_pass_code('', '
[2147:2147:0430/115209.076645:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[2172:2172:0430/115209.534071:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[2147:2147:0430/115211.079771:ERROR:browser_switcher_service.cc(238)] XXX Init()
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 04070407../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall

0407
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0407
')
UNSAFE Emergency workaround; Run in terminal "chromium --no-sandbox" seems to work.
Last edited by Lander1979 on Mon May 11, 2020 12:28 am, edited 1 time in total.
Lander1979
 
Posts: 27
Joined: Thu Jul 11, 2019 7:35 am

Re: [Chromium] Aw, Snap! SIGSEGV

Postby mogwai » Sun May 03, 2020 12:27 pm

I seem to have the exact same problem.
This chromium version is also giving me the "Aw, Snap!" message every few minutes or hours.
I'm running this on a raspberry pi 2b.

I'll try to figure out more, but I'm at a loss at this moment.
mogwai
 
Posts: 18
Joined: Fri Dec 13, 2019 10:25 am

Re: [Chromium] Aw, Snap! SIGSEGV

Postby Praxis » Mon May 04, 2020 12:21 am

I have the same issue. I tried to reinstall an old version of chrome from my cache but the issue persisted. I think this started with a kernel upgrade or mesa upgrade.

If i run chromium with --no-sandbox, it works fine.
$this->bbcode_second_pass_code('', '
[1832:1832:0503/192247.549488:ERROR:browser_switcher_service.cc(238)] XXX Init()
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[1832:1841:0503/192312.108961:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.')
Praxis
 
Posts: 7
Joined: Thu Dec 26, 2019 5:13 am

Re: [Chromium] Aw, Snap! SIGSEGV

Postby freestyler » Mon May 04, 2020 8:38 am

Same error for me after upgrading.
For now I start the browser with the --disable-seccomp-filter-sandbox flag.

$this->bbcode_second_pass_code('', '$ chromium
[1414:1414:0504/104657.307712:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[1414:1414:0504/104657.492558:ERROR:browser_switcher_service.cc(238)] XXX Init()
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[1414:1459:0504/104657.675704:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1414:1459:0504/104657.677302:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1414:1459:0504/104657.678396:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1438:1438:0504/104658.058527:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403')
freestyler
 
Posts: 2
Joined: Sun Jul 21, 2019 12:38 pm

Re: [Chromium] Aw, Snap! SIGSEGV

Postby Praxis » Wed May 06, 2020 11:31 pm

issue persists with chromium 81.0.4044.138-1
$this->bbcode_second_pass_code('', '
[2386:2386:0506/183023.643097:ERROR:browser_switcher_service.cc(238)] XXX Init()
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403')
Praxis
 
Posts: 7
Joined: Thu Dec 26, 2019 5:13 am

Re: [Chromium] Aw, Snap! SIGSEGV

Postby Lander1979 » Sat May 09, 2020 1:25 am

For me the behaviour has changed. Since last update; Chromium crashes immediately without being able to load at all. running on rpi 3b+.

Chromium Version 81.0.4044.138 (Official Build) Arch Linux ARM (32-bit).

Terminal output has changed to;
$this->bbcode_second_pass_code('', '
[1079:1079:0509/103122.839715:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[1079:1079:0509/103124.497399:ERROR:browser_switcher_service.cc(238)] XXX Init()
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[1079:1088:0509/103158.034300:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)
')
Lander1979
 
Posts: 27
Joined: Thu Jul 11, 2019 7:35 am

Re: [Chromium] Aw, Snap! SIGSEGV

Postby Praxis » Sat May 09, 2020 1:42 am

Issue still persists with chromium 81.0.4044.138-2 update

$this->bbcode_second_pass_code('', '[2037:2037:0508/204309.314318:ERROR:browser_switcher_service.cc(238)] XXX Init()
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
')
Praxis
 
Posts: 7
Joined: Thu Dec 26, 2019 5:13 am

Re: [Chromium] Aw, Snap! SIGSEGV

Postby ivanich » Sat May 09, 2020 9:18 pm

Fixed with 81.0.4044.138-2.1
ivanich
 
Posts: 10
Joined: Wed Dec 04, 2019 3:00 pm

Re: [Chromium] Aw, Snap! SIGSEGV

Postby Praxis » Sat May 09, 2020 10:09 pm

Fixed with chromium 81.0.4044.138-2.1
Thank you if it was someone here that fixed it. :D
Praxis
 
Posts: 7
Joined: Thu Dec 26, 2019 5:13 am

Re: [Chromium] Aw, Snap! SIGSEGV

Postby Lander1979 » Mon May 11, 2020 12:25 am

Fixed in the latest update. Chromium is back to normal now.
Marking thread as SOLVED.
Lander1979
 
Posts: 27
Joined: Thu Jul 11, 2019 7:35 am


Return to Packages

Who is online

Users browsing this forum: No registered users and 6 guests