Bugzilla – Bug 966082
chromium: sandbox related stacktrace printed
Last modified: 2016-06-30 14:17:43 UTC
Warning seen on openSUSE 13.2 x86_64 with chromium-48.0.2564.103-823.1.x86_64 (network:chromium/chromium) and other versions when run from the shell. Discussed in bug 965356 comment #17 and bug 965356 comment #26 but found to be unrelated. 13893:13893:0210/172349:FATAL:sandbox_seccomp_bpf_linux.cc(203)] Check failed: policy->PreSandboxHook(). #0 0x7f2dd9eb46be base::debug::StackTrace::StackTrace() #1 0x7f2dd9ecfe27 logging::LogMessage::~LogMessage() #2 0x7f2de122ed1b content::SandboxSeccompBPF::StartSandbox() #3 0x7f2de122dfba content::LinuxSandbox::StartSeccompBPF() #4 0x7f2de122e304 content::LinuxSandbox::InitializeSandboxImpl() #5 0x7f2de12347ed content::(anonymous namespace)::StartSandboxLinux() #6 0x7f2de1236076 content::GpuMain() #7 0x7f2de0ccf775 content::ContentMainRunnerImpl::Run() #8 0x7f2de0ccecf1 content::ContentMain() #9 0x7f2de55d6748 ChromeMain #10 0x7f2dd0ad2b05 __libc_start_main #11 0x7f2de55d6615 <unknown> Received signal 6 #0 0x7f2dd9eb46be base::debug::StackTrace::StackTrace() #1 0x7f2dd9eb47a3 base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x7f2dd0e67890 <unknown> #3 0x7f2dd0ae6187 __GI_raise #4 0x7f2dd0ae7538 __GI_abort #5 0x7f2dd9eb31b5 base::debug::BreakDebugger() #6 0x7f2dd9ecfeb5 logging::LogMessage::~LogMessage() #7 0x7f2de122ed1b content::SandboxSeccompBPF::StartSandbox() #8 0x7f2de122dfba content::LinuxSandbox::StartSeccompBPF() #9 0x7f2de122e304 content::LinuxSandbox::InitializeSandboxImpl() #10 0x7f2de12347ed content::(anonymous namespace)::StartSandboxLinux() #11 0x7f2de1236076 content::GpuMain() #12 0x7f2de0ccf775 content::ContentMainRunnerImpl::Run() #13 0x7f2de0ccecf1 content::ContentMain() #14 0x7f2de55d6748 ChromeMain #15 0x7f2dd0ad2b05 __libc_start_main #16 0x7f2de55d6615 <unknown> r8: ffff95fcb0a81168 r9: ffff95fcb0a81158 r10: 0000000000000008 r11: 0000000000000202 r12: 00007ffe58e38238 r13: 0000000000000000 r14: 00007ffe58e37dd0 r15: 00000000000000de di: 0000000000003645 si: 0000000000003645 bp: 00007f2dd18943e0 bx: 00007ffe58e38230 dx: 0000000000000006 ax: 0000000000000000 cx: ffffffffffffffff sp: 00007ffe58e37a48 ip: 00007f2dd0ae6187 efl: 0000000000000202 cgf: 6733000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace]
Hi Andreas, Would it be possible for you to try the chromium build from the network:chromium repository ? I wonder if this is caused by also the system libs (as the other bug) or that it is the patch to use the accelerated Video (libva). Thanks
(In reply to Raymond Wooninck from comment #1) > Would it be possible for you to try the chromium build from the > network:chromium repository ? I wonder if this is caused by also the system > libs (as the other bug) or that it is the patch to use the accelerated Video > (libva). This was from network:chromium, chromium-48.0.2564.103-823.1.x86_64, last changelog: - Drop building with systemslibs. This is causing issues.
It seems GPU code related. chrome://gpu shows the following for current chromium-48.0.2564.82-67.1.x86_64 -->-- Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only. Hardware acceleration disabled Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable [...] Log Messages GpuProcessHostUIShim: The GPU process exited with code 256. --<-- Whereas the same on (most current) google-chrome-stable-48.0.2564.109-1.x86_64 gives some acceleration and no real errors: -->-- Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Rasterization: Software only. Hardware acceleration disabled Video Decode: Software only, hardware acceleration unavailable Video Encode: Hardware accelerated WebGL: Hardware accelerated --<--
(In reply to Andreas Stieger from comment #2) > (In reply to Raymond Wooninck from comment #1) > > Would it be possible for you to try the chromium build from the > > network:chromium repository ? I wonder if this is caused by also the system > > libs (as the other bug) or that it is the patch to use the accelerated Video > > (libva). > > This was from network:chromium, chromium-48.0.2564.103-823.1.x86_64, last > changelog: > - Drop building with systemslibs. This is causing issues. For completeness, same one this one from network:chromium: chromium-48.0.2564.103-826.1.x86_64 > - Drop completely the option to build with system libraries. This > could lead to issues (boo#965738)
Ok. Thanks for testing. At least we can rule out the system libs. This leaves only one thing that could cause this and this would be the patch that activates libva (VAAPI) support. Also comment#3 points towards this as that it seems GPU related. As that this issue does not occur on Leap nor Tumbleweed, I will change the logic in the spec-file to not apply the patch on openSUSE 13.2. Once it got build we can test again. Thanks
Andreas, Could you have a look with the latest build in network:chromium for openSUSE 13.2 ? IF this still generates the issue, then it must be a kernel issue as that the build is then equal to the ones delivered before the kernel updates. Thanks
That fixes the issue, message no longer printed with that build. $ rpm -q --changelog chromium | head -n3 * Thu Feb 11 2016 tittiatcoke@gmail.com - Don't build with libva support for openSUSE 13.2 and lower (boo#966082) $ rpm -q chromium chromium-48.0.2564.103-828.1.x86_64
*** Bug 965566 has been marked as a duplicate of this bug. ***
(In reply to Wolfgang Bauer from comment #8) > *** Bug 965566 has been marked as a duplicate of this bug. *** Apparently this is not only an issue on 13.2, but also Leap 42.1...
This is an autogenerated message for OBS integration: This bug (966082) was mentioned in https://build.opensuse.org/request/show/359487 13.1 / chromium
openSUSE-SU-2016:0491-1: An update that fixes 6 vulnerabilities is now available. Category: security (moderate) Bug References: 965566,965738,965999,966082 CVE References: CVE-2016-1622,CVE-2016-1623,CVE-2016-1624,CVE-2016-1625,CVE-2016-1626,CVE-2016-1627 Sources used: SUSE Package Hub for SUSE Linux Enterprise 12 (src): chromium-48.0.2564.109-49.1
openSUSE-SU-2016:0518-1: An update that fixes 6 vulnerabilities is now available. Category: security (moderate) Bug References: 965566,965738,965999,966082 CVE References: CVE-2016-1622,CVE-2016-1623,CVE-2016-1624,CVE-2016-1625,CVE-2016-1626,CVE-2016-1627 Sources used: openSUSE 13.1 (src): chromium-48.0.2564.109-125.1