Issue metadata
Sign in to add a comment
|
Chromium does not start due to "Check failed: sandbox::ThreadHelpers::IsSingleThreaded()"
Reported by
fuant...@gmail.com,
Apr 4 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 Steps to reproduce the problem: Try launching browser What is the expected behavior? What went wrong? Browser crashes Crashed report ID: No How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes Chrome version: 65.0.3325.181 Channel: stable OS Version: Gentoo Flash Version: I have made a fresh system (Gentoo) rebuild, tried building Chromium with both GCC and Clang, tried 66.0.3359.66 beta version, they all fail to start, but I think this version worked at some point before breaking. Unfortunately, I don't know what to try next. [1:1:0404/191834.798473:FATAL:zygote_main_linux.cc(283)] Check failed: sandbox::ThreadHelpers::IsSingleThreaded(). #0 0x5652cbf8bbcc <unknown> #1 0x5652cbfa35de <unknown> #2 0x5652caa8ddf6 <unknown> #3 0x5652cbc544a8 <unknown> #4 0x5652cbc554f1 <unknown> #5 0x5652cbc5f327 <unknown> #6 0x5652cbc543f4 <unknown> #7 0x5652ca202ca5 ChromeMain #8 0x7fb0365f8eec __libc_start_main #9 0x5652ca202b5a _start Received signal 6 #0 0x5652cbf8bbcc <unknown> #1 0x5652cbf8b731 <unknown> #2 0x7fb040c33f10 <unknown> #3 0x7fb03660d940 gsignal #4 0x7fb03660f476 abort #5 0x5652cbf89f45 <unknown> #6 0x5652cbfa38ca <unknown> #7 0x5652caa8ddf6 <unknown> #8 0x5652cbc544a8 <unknown> #9 0x5652cbc554f1 <unknown> #10 0x5652cbc5f327 <unknown> #11 0x5652cbc543f4 <unknown> #12 0x5652ca202ca5 ChromeMain #13 0x7fb0365f8eec __libc_start_main #14 0x5652ca202b5a _start r8: 0000000000000000 r9: 00007ffd337646b0 r10: 0000000000000008 r11: 0000000000000246 r12: 00007fb036fb1cc0 r13: 00007ffd33764e18 r14: 0000000000000073 r15: 00007ffd33764e10 di: 0000000000000002 si: 00007ffd337646b0 bp: 00007ffd33764900 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00007fb03660d940 sp: 00007ffd337646b0 ip: 00007fb03660d940 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated. [12119:12119:0404/191834.803846:FATAL:zygote_host_impl_linux.cc(209)] Check failed: ReceiveFixedMessage(fds[0], kZygoteHelloMessage, sizeof(kZygoteHelloMessage), &real_pid). #0 0x563992728bcc <unknown> #1 0x5639927405de <unknown> #2 0x5639916e775e <unknown> #3 0x5639912c4358 <unknown> #4 0x5639916e6847 <unknown> #5 0x56399176019d <unknown> #6 0x5639912bebaa <unknown> #7 0x5639912c4f72 <unknown> #8 0x5639912be23f <unknown> #9 0x5639923f24f1 <unknown> #10 0x5639923fc327 <unknown> #11 0x5639923f13f4 <unknown> #12 0x56399099fca5 ChromeMain #13 0x7f7ad8c28eec __libc_start_main #14 0x56399099fb5a _start Received signal 6 #0 0x563992728bcc <unknown> #1 0x563992728731 <unknown> #2 0x7f7ae3263f10 <unknown> #3 0x7f7ad8c3d940 gsignal #4 0x7f7ad8c3f476 abort #5 0x563992726f45 <unknown> #6 0x5639927408ca <unknown> #7 0x5639916e775e <unknown> #8 0x5639912c4358 <unknown> #9 0x5639916e6847 <unknown> #10 0x56399176019d <unknown> #11 0x5639912bebaa <unknown> #12 0x5639912c4f72 <unknown> #13 0x5639912be23f <unknown> #14 0x5639923f24f1 <unknown> #15 0x5639923fc327 <unknown> #16 0x5639923f13f4 <unknown> #17 0x56399099fca5 ChromeMain #18 0x7f7ad8c28eec __libc_start_main #19 0x56399099fb5a _start r8: 0000000000000000 r9: 00007ffc7587ce70 r10: 0000000000000008 r11: 0000000000000246 r12: 00007f7ad95e1cc0 r13: 00007ffc7587d660 r14: 00000000000000ae r15: 00007ffc7587d658 di: 0000000000000002 si: 00007ffc7587ce70 bp: 00007ffc7587d0c0 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00007f7ad8c3d940 sp: 00007ffc7587ce70 ip: 00007f7ad8c3d940 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated.
,
Apr 5 2018
Thanks for filing the issue. Could you please provide us the crash Report id(16 digit) from chrome://crashes to triage the issue further.
,
Apr 5 2018
There is no crash id since browser does not start i.e. crashes when starting.
,
Apr 5 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 6 2018
Sounds like it might be a system library you have installed that is spawning a thread in the sandbox process. See comment here: https://cs.chromium.org/chromium/src/content/zygote/zygote_main_linux.cc?sq=package:chromium&l=283 that you are failing. Maybe the sandbox folks have an idea.
,
Apr 7 2018
If I understand this correctly chrome has only main thread, lots of gpu threads and sandbox thread when it crashes. Below are (gdb) run (gdb) thread apply all bt (gdb) run Starting program: /usr/lib64/chromium-browser/chrome [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffcfc7b700 (LWP 19925)] [New Thread 0x7fffcf26e700 (LWP 19926)] [New Thread 0x7fffcea6d700 (LWP 19927)] [New Thread 0x7fffce26c700 (LWP 19928)] [New Thread 0x7fffcda6b700 (LWP 19929)] [New Thread 0x7fffcd26a700 (LWP 19930)] [New Thread 0x7fffcca69700 (LWP 19931)] [New Thread 0x7fffb7fff700 (LWP 19932)] [New Thread 0x7fffb77fe700 (LWP 19933)] [New Thread 0x7fffb6ffd700 (LWP 19934)] [New Thread 0x7fffb67fc700 (LWP 19935)] [Thread 0x7fffb77fe700 (LWP 19933) exited] [Thread 0x7fffb6ffd700 (LWP 19934) exited] [Thread 0x7fffb7fff700 (LWP 19932) exited] [Thread 0x7fffb67fc700 (LWP 19935) exited] [New Thread 0x7fffb67fc700 (LWP 19936)] [1:1:0407/221223.741327:FATAL:zygote_main_linux.cc(283)] Check failed: sandbox::ThreadHelpers::IsSingleThreaded(). #0 0x555557f59bcc <unknown> #1 0x555557f715de <unknown> #2 0x555556a5bdf6 <unknown> #3 0x555557c224a8 <unknown> #4 0x555557c234f1 <unknown> #5 0x555557c2d327 <unknown> #6 0x555557c223f4 <unknown> #7 0x5555561d0ca5 ChromeMain #8 0x7fffed659eec __libc_start_main #9 0x5555561d0b5a _start Received signal 6 #0 0x555557f59bcc <unknown> #1 0x555557f59731 <unknown> #2 0x7ffff7bcbee0 <unknown> #3 0x7fffed66e940 gsignal #4 0x7fffed670476 abort #5 0x555557f57f45 <unknown> #6 0x555557f718ca <unknown> #7 0x555556a5bdf6 <unknown> #8 0x555557c224a8 <unknown> #9 0x555557c234f1 <unknown> #10 0x555557c2d327 <unknown> #11 0x555557c223f4 <unknown> #12 0x5555561d0ca5 ChromeMain #13 0x7fffed659eec __libc_start_main #14 0x5555561d0b5a _start r8: 0000000000000000 r9: 00007fffffffcb10 r10: 0000000000000008 r11: 0000000000000246 r12: 00007fffee010cc0 r13: 00007fffffffd278 r14: 0000000000000073 r15: 00007fffffffd270 di: 0000000000000002 si: 00007fffffffcb10 bp: 00007fffffffcd60 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00007fffed66e940 sp: 00007fffffffcb10 ip: 00007fffed66e940 efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000001 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated. [19921:19921:0407/221223.748381:FATAL:zygote_host_impl_linux.cc(209)] Check failed: ReceiveFixedMessage(fds[0], kZygoteHelloMessage, sizeof(kZygoteHelloMessage), &real_pid). Thread 1 "chrome" received signal SIGABRT, Aborted. 0x00007fffed66e940 in raise () from /lib64/libc.so.6 (gdb) thread apply all bt Thread 13 (Thread 0x7fffb67fc700 (LWP 19936)): #0 0x00007fffed72d565 in poll () from /lib64/libc.so.6 #1 0x0000555556e13e32 in ?? () #2 0x00000001000000ed in ?? () #3 0x00000001000000ec in ?? () #4 0x00007fffa4000bb0 in ?? () #5 0x221c88dcaca60600 in ?? () #6 0x0000000000000006 in ?? () #7 0x0000000000000019 in ?? () #8 0x00007fffa4000020 in ?? () #9 0x00007fffa4000b80 in ?? () #10 0x00007fffa4000dc0 in ?? () #11 0x0000000000000019 in ?? () #12 0x00007fffa4000d90 in ?? () #13 0x00007fffed6c0e85 in malloc () from /lib64/libc.so.6 #14 0x00007fffa4000db0 in ?? () #15 0x00007fffa4000c28 in ?? () #16 0x00007fffa4000dc0 in ?? () #17 0x0000000000000018 in ?? () #18 0x00007fffa4000d90 in ?? () #19 0x00007fffb67fbab0 in ?? () #20 0x0000555557fc1d6c in ?? () #21 0x00007fffa4000c30 in ?? () #22 0x00007fffa4000c28 in ?? () #23 0x0000000000000018 in ?? () #24 0x0000000000000018 in ?? () #25 0x00007fffa4000c30 in ?? () #26 0x00007fffa4000b80 in ?? () #27 0x0000000000000000 in ?? () Thread 8 (Thread 0x7fffcca69700 (LWP 19931)): #0 0x00007ffff7bc6675 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fffd05d279b in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #2 0x00007fffd05d24cf in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #3 0x00007ffff7bbf8ba in start_thread () from /lib64/libpthread.so.0 #4 0x00007fffed738d0f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fffcd26a700 (LWP 19930)): #0 0x00007ffff7bc6675 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fffd05d279b in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #2 0x00007fffd05d24cf in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #3 0x00007ffff7bbf8ba in start_thread () from /lib64/libpthread.so.0 #4 0x00007fffed738d0f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fffcda6b700 (LWP 19929)): #0 0x00007ffff7bc6675 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fffd05d279b in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #2 0x00007fffd05d24cf in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #3 0x00007ffff7bbf8ba in start_thread () from /lib64/libpthread.so.0 #4 0x00007fffed738d0f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fffce26c700 (LWP 19928)): #0 0x00007ffff7bc6675 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fffd05d279b in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #2 0x00007fffd05d24cf in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #3 0x00007ffff7bbf8ba in start_thread () from /lib64/libpthread.so.0 #4 0x00007fffed738d0f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fffcea6d700 (LWP 19927)): #0 0x00007ffff7bc6675 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fffd05d279b in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #2 0x00007fffd05d24cf in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #3 0x00007ffff7bbf8ba in start_thread () from /lib64/libpthread.so.0 #4 0x00007fffed738d0f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fffcf26e700 (LWP 19926)): ---Type <return> to continue, or q <return> to quit--- #0 0x00007ffff7bc6675 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fffd05d279b in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #2 0x00007fffd05d24cf in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #3 0x00007ffff7bbf8ba in start_thread () from /lib64/libpthread.so.0 #4 0x00007fffed738d0f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fffcfc7b700 (LWP 19925)): #0 0x00007ffff7bc6675 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fffd05d279b in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #2 0x00007fffd05d24cf in ?? () from /usr/lib64/gallium-pipe/pipe_radeonsi.so #3 0x00007ffff7bbf8ba in start_thread () from /lib64/libpthread.so.0 #4 0x00007fffed738d0f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ffff7f6ca00 (LWP 19921)): #0 0x00007fffed66e940 in raise () from /lib64/libc.so.6 #1 0x00007fffed670476 in abort () from /lib64/libc.so.6 #2 0x0000555557f57f45 in ?? () #3 0x00007fffffffca40 in ?? () #4 0x0000555557f718ca in ?? () #5 0x3fd314f1e1d35ce0 in ?? () #6 0x0000000000000000 in ?? ()
,
Apr 10 2018
Could some one from sandbox team please take a look into this issue as per C#5. Thanks..!
,
Apr 19 2018
Well, according to more experienced Gentoo folks the problems lies in ffmpeg built with opencl support https://bugs.gentoo.org/651988 Gonna try this one later today
,
Apr 19 2018
Yep. With system ffmpeg built without opencl support chromium works fine.
,
Apr 23 2018
fuantaji@ As per comment #9, shall we close this issue.
,
Apr 23 2018
This is a workaround, not a fix really. While chromium has bundled ffmpeg should it also work with system one? And if it was built with opencl support? If this will be expected behavior of ffmpeg to spawn more than one thread for opencl support.
,
Apr 23 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by fuant...@gmail.com
, Apr 4 2018