Also experiencing this issue on Armbian / Tinkerboard: (started in the
last 24 hours)

Received signal 4 <unknown> 0000b627bf76
#0 0x0000b6ecfd12 base::debug::StackTrace::StackTrace()
#1 0x0000b6ecf952 base::debug::StackTrace::StackTrace()
#2 0x0000b6ecfffc <unknown>
#3 0x0000b22c4270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[1:1:0100/000000.254673:ERROR:broker_posix.cc(41)] Invalid node channel message
[1:1:0100/000000.254358:ERROR:broker_posix.cc(41)] Invalid node channel message
[1:1:0100/000000.252931:ERROR:broker_posix.cc(41)] Invalid node channel message
chromium-browser --type=renderer --enable-pinch --touch-events=enabled 
--field-trial-handle=1 --primordial-pipe-token=4F4CE9017E684C5B2C348A144C447C52 
--lang=en-US --extension-process --enable-offline-auto-reload 
--enable-offline-auto-reload-visible-only --enable-pinch --num-raster-threads=2 
--enable-main-frame-before-activation 
--content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;3,0,3553:
 pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == 
thread->tid' failed.
chromium-browser --type=renderer --enable-pinch --touch-events=enabled 
--field-trial-handle=1 --primordial-pipe-token=5C7F09F5E933838E9FA003036790C6CA 
--lang=en-US --extension-process --enable-offline-auto-reload 
--enable-offline-auto-reload-visible-only --enable-pinch --num-raster-threads=2 
--enable-main-frame-before-activation 
--content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;3,0,3553:
 pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == 
thread->tid' failed.
Received signal Received signal 44 <unknown>  <unknown> 0000b223e3f60000b223e3f6

##00  0x0x0000b6e49d120000b6e49d12  <unknown>
#1 0x0000b6e49952 <unknown>
ile5ErrorE#
2# 10x 0000b6e49ffc0x 0000b6e49952 <unknown>
#2 0x0000b6e49ffc <unknown>peEPi

##33  0x0x0000b223e2700000b223e270  <unknown>
#4 0x0000b223e3f6 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.

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

Title:
  Google chrome cannot start with Raspberry Pi 3 Ubuntu-Mate 16.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702633/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to