Discussion:
[Bug 1563184] [NEW] InitializeSandbox() called with multiple threads in process gpu-process
David Burke
2016-03-29 05:29:05 UTC
Permalink
Public bug reported:

crashes on startup with

[2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process
Segmentation fault

System ODROID XU3 armhf

** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
InitializeSandbox() called with multiple threads in process gpu-
process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Nonny Moose
2016-04-03 14:39:43 UTC
Permalink
I have had almost the exact same problem on a Raspberry Pi 2 running Ubuntu Mate 15.10.
uname -a:
Linux RaspberryPi 3.18.0-20-rpi2 #21-Ubuntu SMP PREEMPT Sun Apr 5 01:56:02 UTC 2015 armv7l armv7l armv7l GNU/Linux

$ chromium-browser
[2815:2815:0403/092234:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process
Segmentation fault (core dumped)

** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
InitializeSandbox() called with multiple threads in process gpu-
process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Aworan
2016-04-05 16:42:51 UTC
Permalink
Same problem here with raspberry pi 2 or raspberry pi 3 under ubuntu mate and lubuntu 15.10.
chromium-browser works before version 49.
If I go back to version 48 it works.
The bug is with armhf architecture package !
The bug is confirmed by ubuntu mate for raspberry pi community users, see :
https://ubuntu-mate.community/t/chromium-crashes-when-starting-segfaults/4578/14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
InitializeSandbox() called with multiple threads in process gpu-
process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ross Holder
2016-04-05 18:19:01 UTC
Permalink
I too am having the same issue as described above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
InitializeSandbox() called with multiple threads in process gpu-
process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
William Woods
2016-04-06 00:26:10 UTC
Permalink
Confirming that I am having the same issue on both an Orange Pi and a
ODroid running Ubuntu Mate 15.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
InitializeSandbox() called with multiple threads in process gpu-
process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Chazall1
2016-04-07 21:01:52 UTC
Permalink
Confirming that I am having the same issue on R-Pi 3 . Running Ubuntu
Mate 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
InitializeSandbox() called with multiple threads in process gpu-
process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Joao Driessen
2016-04-13 20:56:01 UTC
Permalink
Problem also exists in archlinux arm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
InitializeSandbox() called with multiple threads in process gpu-
process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Nonny Moose
2016-04-26 16:27:35 UTC
Permalink
I upgraded my Raspberry Pi 2 to Ubuntu Mate 16.10 LTS and Chromium
continues to segfault when launched from the menu, but when I launched
it from the terminal it opened a completely transparent window that
proceeded to do absolutely nothing. When I finally got impatient and
^Ced it, <i>then</i> it had a segfault and printed out a stack trace,
which was essentially garbage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
InitializeSandbox() called with multiple threads in process gpu-
process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Nonny Moose
2016-05-05 16:10:33 UTC
Permalink
I have had several other bugs have this error:
``

I think that the name should be changed to be more descriptive:

`Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"`

** Summary changed:

- InitializeSandbox() called with multiple threads in process gpu-process
+ Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Simon Jeffrey
2016-05-07 05:18:53 UTC
Permalink
Same issue. RPi3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Remis
2016-05-10 14:21:29 UTC
Permalink
Same issue, RPi3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Tianon Gravi
2016-05-16 23:11:24 UTC
Permalink
Hit the same issue on my own new Raspberry Pi 3 running Ubuntu Xenial
(installed via http://www.finnie.org/software/raspberrypi/ubuntu-
rpi3/ubuntu-16.04-preinstalled-server-armhf+raspi3.img.xz linked from
https://wiki.ubuntu.com/ARM/RaspberryPi).

I managed to get a little bit further by installing the "chromium-
browser" package from "trusty" (which appears to be the same underlying
Chromium version backported; more exactly, package version
"49.0.2623.108-0ubuntu0.14.04.1.1113").

That at least lets the browser come up, but all the pages crash (as
opposed to the entire browser crashing, like the xenial version does).

When I add "--no-sandbox" (which is inherently dangerous and adds an
appropriate warning to the UI every time you launch chrome), I can get
much further and actually have a functional Chromium instance (but using
"--no-sandbox" is obviously pretty far from ideal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Pavel Karateev
2016-05-18 07:17:48 UTC
Permalink
Same here: Debian 8, Mate 1.8.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Tianon Gravi
2016-05-18 14:52:14 UTC
Permalink
The debdiff from xenial to trusty (attached) doesn't appear terribly
interesting. :(

** Patch added: "xenial-to-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+attachment/4665562/+files/xenial-to-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
rusli
2016-05-18 20:48:56 UTC
Permalink
I try Google Chrome OS for SBC ...
From this link
http://www.chromiumosforsbc.org/cros_rpi3-v05-notes

They able to fix html5 video driver and can play youtube without any issues
at all.

Maybe you need to use that OS to debug and fix the issues in ubuntu
mate...

They even use a new kernel for it...
On 18 May 2016 11:01 pm, "Tianon Gravi" <***@gmail.com> wrote:

The debdiff from xenial to trusty (attached) doesn't appear terribly
interesting. :(

** Patch added: "xenial-to-trusty.debdiff"

https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1563184/+attachment/4665562/+files/xenial-to-trusty.debdiff

--
You received this bug notification because you are subscribed to a
duplicate bug report (1576079).
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

Status in chromium-browser package in Ubuntu:
Confirmed

Bug description:
crashes on startup with

[2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox()
called with multiple threads in process gpu-process
Segmentation fault

System ODROID XU3 armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Will Glynn
2016-05-26 00:31:47 UTC
Permalink
I encountered this on a Raspberry Pi 2 running a minimal Ubuntu 16.04.
The initial install was based on ubuntu-16.04-preinstalled-server-
armhf+raspi2.img.xz from https://wiki.ubuntu.com/ARM/RaspberryPi.

Starting chromium-browser 50.0.2661.102-0ubuntu0.16.04.1 (armhf) with no
args, I get:

$ chromium-browser

(chromium-browser:9976): GLib-GIO-CRITICAL **: g_settings_schema_source_lookup: assertion 'source != NULL' failed
[10031:10031:0526/000302:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process

(chromium-browser:9976): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally without any error message
chro: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed.
Received signal 4 <unknown> 0000721733e6
#0 0x000076d9fe1a base::debug::StackTrace::StackTrace()
#1 0x000076da0104 <unknown>
#2 0x000072173260 <unknown>
#3 0x0000721733e6 abort
[end of stack trace]
Segmentation fault

If I allow it to dump core, I get a backtrace:

$ ulimit -c unlimited
$ chromium-browser

(chromium-browser:13589): GLib-GIO-CRITICAL **:
g_settings_schema_source_lookup: assertion 'source != NULL' failed

(chromium-browser:13589): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally without any error message
chro: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed.
Received signal 4 <unknown> 0000721bc3e6
#0 0x000076de8e1a base::debug::StackTrace::StackTrace()
#1 0x000076de9104 <unknown>
#2 0x0000721bc260 <unknown>
#3 0x0000721bc3e6 abort
[end of stack trace]
[13645:13645:0526/002513:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process
Segmentation fault (core dumped)

$ gdb /usr/lib/chromium-browser/chromium-browser core
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11

Core was generated by `chromium-browser --enable-pinch '.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x72426bc6 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
[Current thread is 1 (Thread 0x673c8230 (LWP 13616))]
(gdb) bt
#0 0x72426bc6 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#1 0x5509389c in std::_Rb_tree_iterator<std::pair<unsigned long long const, int> > std::_Rb_tree<unsigned long long, std::pair<unsigned long long const, int>, std::_Select1st<std::pair<unsigned long long const, int> >, std::less<unsigned long long>, std::allocator<std::pair<unsigned long long const, int> > >::_M_emplace_hint_unique<std::piecewise_construct_t const&, std::tuple<unsigned long long const&>, std::tuple<> >(std::_Rb_tree_const_iterator<std::pair<unsigned long long const, int> >, std::piecewise_construct_t const&, std::tuple<unsigned long long const&>&&, std::tuple<>&&) ()
#2 0x553ea784 in ?? ()
#3 0x553eec6c in ?? ()
#4 0x54f04afa in ?? ()
#5 0x741be894 in net::URLRequestHttpJob::StartTransactionInternal() () from /usr/lib/chromium-browser/libs/libnet.so
#6 0x741beb88 in net::URLRequestHttpJob::MaybeStartTransactionInternal(int) () from /usr/lib/chromium-browser/libs/libnet.so
#7 0x741bec00 in net::URLRequestHttpJob::StartTransaction() () from /usr/lib/chromium-browser/libs/libnet.so
#8 0x741bec7c in net::URLRequestHttpJob::AddCookieHeaderAndStart() () from /usr/lib/chromium-browser/libs/libnet.so
#9 0x741bf228 in net::URLRequestHttpJob::Start() () from /usr/lib/chromium-browser/libs/libnet.so
#10 0x741b6a5c in net::URLRequest::StartJob(net::URLRequestJob*) () from /usr/lib/chromium-browser/libs/libnet.so
#11 0x741b7234 in net::URLRequest::BeforeRequestComplete(int) () from /usr/lib/chromium-browser/libs/libnet.so
#12 0x741b7384 in net::URLRequest::Start() () from /usr/lib/chromium-browser/libs/libnet.so
#13 0x741b4a76 in ?? () from /usr/lib/chromium-browser/libs/libnet.so
#14 0x741b4d9c in ?? () from /usr/lib/chromium-browser/libs/libnet.so
#15 0x741b5b94 in net::URLFetcherFileWriter::DidOpenFile(base::Callback<void (int)> const&, int) () from /usr/lib/chromium-browser/libs/libnet.so
#16 0x741b5988 in ?? () from /usr/lib/chromium-browser/libs/libnet.so
#17 0x7409bd7e in ?? () from /usr/lib/chromium-browser/libs/libnet.so
#18 0x7409c3fa in net::FileStream::Context::OnAsyncCompleted(base::Callback<void (long long)> const&, net::FileStream::Context::IOResult const&) () from /usr/lib/chromium-browser/libs/libnet.so
#19 0x7409c4a2 in net::FileStream::Context::OnOpenCompleted(base::Callback<void (int)> const&, net::FileStream::Context::OpenResult) () from /usr/lib/chromium-browser/libs/libnet.so
#20 0x7409c236 in ?? () from /usr/lib/chromium-browser/libs/libnet.so
#21 0x7409c1c0 in ?? () from /usr/lib/chromium-browser/libs/libnet.so
#22 0x76e8494c in ?? () from /usr/lib/chromium-browser/libs/libbase.so
#23 0x76e49e58 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
#24 0x76e5fbba in base::MessageLoop::RunTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
#25 0x76e60090 in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from /usr/lib/chromium-browser/libs/libbase.so
#26 0x76e6023c in base::MessageLoop::DoWork() () from /usr/lib/chromium-browser/libs/libbase.so
#27 0x76e3f524 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/lib/chromium-browser/libs/libbase.so
#28 0x76e71e68 in base::RunLoop::Run() () from /usr/lib/chromium-browser/libs/libbase.so
#29 0x76e5f3d4 in base::MessageLoop::Run() () from /usr/lib/chromium-browser/libs/libbase.so
#30 0x7528aa5c in content::BrowserThreadImpl::IOThreadRun(base::MessageLoop*) () from /usr/lib/chromium-browser/libs/libcontent.so
#31 0x7528af88 in content::BrowserThreadImpl::Run(base::MessageLoop*) () from /usr/lib/chromium-browser/libs/libcontent.so
#32 0x76e87624 in base::Thread::ThreadMain() () from /usr/lib/chromium-browser/libs/libbase.so
#33 0x76e8485c in ?? () from /usr/lib/chromium-browser/libs/libbase.so
#34 0x722e85a4 in start_thread (arg=0x0) at pthread_create.c:335
#35 0x72289cec in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:89 from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

The InitializeSandbox() error here (along with the pthread_getattr_np
error above) appears to be unrelated to this crash. Running `chromium-
browser --disable-gpu --no-sandbox --single-process` avoids calling
InitializeSandbox() from the GPU process, since there's no GPU
acceleration, no sandbox, and only one process, yet it segfaults all the
same:

$ chromium-browser --disable-gpu --no-sandbox --dbus-stub --single-process
[14460:14460:0526/002818:ERROR:browser_main_loop.cc(219)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.

(chromium-browser:14460): GLib-GIO-CRITICAL **: g_settings_schema_source_lookup: assertion 'source != NULL' failed
[14460:14482:0526/002821:ERROR:proxy_service_factory.cc(130)] Cannot use V8 Proxy resolver in single process mode.
[14460:14482:0526/002822:ERROR:proxy_service_factory.cc(130)] Cannot use V8 Proxy resolver in single process mode.

(chromium-browser:14460): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
/usr/bin/dbus-launch terminated abnormally without any error message
Segmentation fault (core dumped)

The backtrace from this invocation appears identical to the above,
confirming that the InitializeSandbox() error is a red herring, at least
on my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailm
Liam Proven
2016-05-27 16:12:19 UTC
Permalink
Replicated on Lubuntu 16.04 on RasPi 3. Fully updated, Chromium 50
segfaults.

--no-sandbox does not work; still segfaults.

As per this page:
https://ubuntu-mate.community/t/chromium-crashes-when-starting-segfaults/4578

I also tried --disable-pinch. Doesn't work; still segfaults.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
mordant
2016-05-30 06:09:33 UTC
Permalink
To provide more information, the specific stacktrace that breaks the sandbox is:
[2781:2861:0529/230241:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 2956: Permission denied
[2781:2861:0529/230241:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 2997: Permission denied
[2781:2861:0529/230241:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 2998: Permission denied
[2781:2861:0529/230241:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 3000: Permission denied
[2781:2861:0529/230241:ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer with pid 3004: Permission denied
Segmentation fault (core dumped)
***@bbliveservice-desktop:~$ [2948:2948:0529/230244:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process

This indicates it may have to do with
https://bugs.chromium.org/p/chromium/issues/detail?id=576409
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Nonny Moose
2016-05-28 19:18:28 UTC
Permalink
I was aware that the InitializeSandbox error was not related to the issue because I get that from like half of my applications. XD
The chromium-browser <i>script</i> that starts chromium-browser supports the flag --no-touch-pinch, which I find a little odd because it essentially turns it into --disable-pinch when it sends the flags to the binary itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Davide Alberelli
2016-07-24 14:00:02 UTC
Permalink
Same here with 16.04 on RaspberryPi 3 and Chromium
51.0.2704.79-0ubuntu0.16.04.1.1242.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Chad Miller
2016-07-25 01:26:06 UTC
Permalink
Reproduced. Thanks, all. I don't need more me-toos for now.

** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => High

** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Chad Miller (cmiller)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Nonny Moose
2016-08-13 15:26:07 UTC
Permalink
@cmiller If you need any impersonal information about the crash on my
system, I would be happy to porvide it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
bandyt
2016-09-20 07:44:45 UTC
Permalink
I also reached to this ticket and I will be happy of any progress.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Francesco Strappini
2016-09-22 15:47:58 UTC
Permalink
Same here with Xubuntu 16.04 on RPi 3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Jasen Stoeker
2016-09-24 03:54:57 UTC
Permalink
I'm also subscribing. Just bought my first Raspberry Pi 3b, and
installed Lubuntu 16.04 on it, and I have the exact same error message
when trying to start Chrome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Tony U.
2016-10-18 02:01:22 UTC
Permalink
Man, this bug is a big show stopper for me. I use Chromium on my
RaspPi-3 to turn my local printer into a cloud ready printer, and I have
not been able to use this feature since this bug came about.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Russell Faull
2016-10-18 02:59:48 UTC
Permalink
@Tony U Workaround using older version of Chromium for RPI is at https
://ubuntu-mate.community/t/trying-to-fix-chromium-issues/9235/10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Xavier
2016-10-18 03:23:28 UTC
Permalink
I was experiencing this bug as well on my Odroid XU3.
Eventually, I switched to Firefox and that works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Henry Wertz
2016-11-04 18:14:52 UTC
Permalink
I wonder if this is a compiler error? Can anyone tell if Chromium for
Ubuntu 14.04 and Chromium for 16.04 have different build flags, or if
their configure scripts detect something different? To me, it seems
like if they have the same or very similar build flags, 16.04 build
breaks but 14.04 build doesn't, it implies gcc-5.4 is misbuilding
something that gcc-4.8 isn't (or, much less likely, gcc-5.4 is building
something correctly but chromium relies on some misbehavior of older
gcc.)

I have an Acer Chromebook 13 (Tegra K1) which had 14.04 on it; Chromium
52 or 53 worked fine. Went to 16.04 (managing to hold back X so I could
keep the nvidia driver...) and chromium blew up as others have reported.

I also found the 14.04 build of (at this point, chromium 53) worked fine
after I set "--disable-namespace-sandbox"... I had the "Aw, snap!" but
found (per google) that "--disable-namespace-sandbox" fixed it without
the ill effects of "--no-sandbox".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Lionel Porcheron
2017-06-20 13:37:33 UTC
Permalink
For the record, it works on an Ubuntu 17.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Adam Smith
2017-09-11 21:06:42 UTC
Permalink
I can confirm armhf and arm64 chromium works in 17.04

This is on a raspberry pi 3. On 16.04 chromium displays "aw, snap"
unless I start with --no-sandbox

These https://github.com/raspberrypi-ui/chromium_patches are the patches
used in raspbian. I don't know if there is anything useful in there to
do with this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lis
Adam Smith
2017-09-12 08:02:38 UTC
Permalink
Just to clarify, I've only tested 16.04 on armhf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.c
Olivier Tilloy
2018-03-09 13:42:46 UTC
Permalink
** Changed in: chromium-browser (Ubuntu)
Assignee: Chad Miller (cmiller) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://l
Kurt Vogt
2018-03-26 13:08:54 UTC
Permalink
crashes on startup with

[ATTENTION: default value of option force_s3tc_enable overridden by environment.
[4005:4005:0326/150642.816056:ERROR:sandbox_linux.cc(375)] InitializeSandbox() called with multiple threads in process gpu-process.

System XUbuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563184

Title:
Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-***@lists.ubuntu.com
https://lists.
Loading...