New issue
Advanced search Search tips

Issue 923570 link

Starred by 3 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Chrome debug build crashes with sandbox error

Project Member Reported by ddavenp...@chromium.org, Jan 18 (4 days ago)

Issue description

Chrome Version: 73.0.3669.0
OS: Chrome OS

What steps will reproduce the problem?
(1) Build a debug build (with DCHECK enabled)
(2) Deploy and run on a chromebook

What is the expected result?
Get to login screen


What happens instead?
GPU process crashes.

From what I can tell, the problem is that the AssertMemoryIsReadOnly function (protected_memory_posix.cc) class calls getrlimit, which is not allowed to be called.

Callstack from the log:
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0302
Received signal 11 SEGV_MAPERR 00000060012e
#0 0x5ae730a386dc [3481:3481:0118/152631.135357:VERBOSE1:login_display_mojo.cc(63)] Emitting login-prompt-visible
[3481:3481:0118/152631.135625:VERBOSE1:arc_session_runner.cc(160)] Session start requested: MINI_INSTANCE
[3481:3481:0118/152631.135691:VERBOSE1:arc_session_runner.cc(233)] Starting ARC instance
[3481:3481:0118/152631.135893:VERBOSE1:arc_session_impl.cc(374)] Starting ARC mini instance with lcd_density=160
base::debug::StackTrace::StackTrace()
#1 0x5ae73079e3b5 [3481:3481:0118/152631.247464:ERROR:object_proxy.cc(621)] Failed to call method: org.chromium.CryptohomeInterface.NeedsDircryptoMigration: object_path= /org/chromium/Cryptohome: org.freedesktop.DBus.GLib.ErrorError: Method invoked for NeedsDircryptoMigration returned FALSE but did not set error
[3481:3481:0118/152631.247627:ERROR:user_selection_screen.cc(331)] Failed to call cryptohome NeedsDircryptoMigration.
base::debug::StackTrace::StackTrace()
#2 0x5ae730a38124 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7e8711a3cab0 <unknown>
#4 0x5ae734e98dac sandbox::CrashSIGSYS_Handler()
#5 0x5ae734ea0dbb sandbox::Trap::SigSys()
#6 0x5ae734ea0a4c sandbox::Trap::SigSysAction()
#7 0x7e8711a3cab0 <unknown>
#8 0x7e8710626e80 __getrlimit
#9 0x5ae730bd8ea9 [3481:3598:0118/152631.744977:WARNING:drm_device_handle.cc(86)] Failed to authenticate /dev/dri/card0 within 1000 ms
base::AssertMemoryIsReadOnly()
#10 0x5ae730bd7c45 base::AutoWritableMemory::AutoWritableMemory()
#11 0x5ae730bd8887 base::AutoWritableMemory::Create<>()
#12 0x5ae7337e4b3f gl::SetGLGetProcAddressProc()
#13 0x5ae728276074 ui::(anonymous namespace)::LoadEGLGLES2Bindings()
#14 0x5ae728275c44 ui::LoadDefaultEGLGLES2Bindings()
#15 0x5ae728203217 ui::(anonymous namespace)::GLOzoneEGLGbm::LoadGLES2Bindings()
#16 0x5ae72827656c ui::GLOzoneEGL::InitializeStaticGLBindings()
#17 0x5ae7340bedb7 gl::init::InitializeStaticGLBindings()
#18 0x5ae7340b99af gl::init::InitializeGLOneOffImplementation()
#19 0x5ae7340b97b5 gl::init::(anonymous namespace)::InitializeGLOneOffHelper()
#20 0x5ae7340b9910 gl::init::InitializeGLNoExtensionsOneOff()
#21 0x5ae7341622fc gpu::GpuInit::InitializeAndStartSandbox()
#22 0x5ae73decf43b content::GpuMain()
#23 0x5ae72f964482 content::RunOtherNamedProcessTypeMain()
#24 0x5ae72f966449 content::ContentMainRunnerImpl::Run()
#25 0x5ae72f95b6bc content::ContentServiceManagerMainDelegate::RunEmbedderProcess()
#26 0x5ae72f97aeea service_manager::Main()
#27 0x5ae72f961bb3 content::ContentMain()
#28 0x5ae7260a1298 ChromeMain
#29 0x5ae7260a1182 main
#30 0x7e8710553ad4 __libc_start_main
#31 0x5ae7260a102a _start
  r8: 000000000000e000  r9: 00007ffc3fffdfd0 r10: 00007ffc3fffdfd0 r11: 00007e87106bd320
 r12: 00005ae740267480 r13: 00007ffc40003570 r14: 0000000000000000 r15: 0000000000000000
  di: 000000000060012e  si: 000000000060012e  bp: 00007ffc3fffe070  bx: 0cc2eced0b35e700
  dx: 0cc2eced0b35e700  ax: 000000000060012e  cx: 0cc2eced0b35e700  sp: 00007ffc3fffe040
  ip: 00005ae734e98dac efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000006
 trp: 000000000000000e msk: 0000000000000000 cr2: 000000000060012e
[end of stack trace]
 

Comment 1 by jorgelo@chromium.org, Today (15 hours ago)

TBH debug builds crashing is... not great. Until we figure things out further, we should probably allow getrlimit in the GPU sandbox.

Comment 2 by jorgelo@chromium.org, Today (13 hours ago)

Also, what Chromebooks does this happen with?

Sign in to add a comment