Bug ID 1124707
Summary chromium crashes after latest tumbleweed update
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component X11 Applications
Assignee bnc-team-screening@forge.provo.novell.com
Reporter arun@gmx.de
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Hi

I just updated to the latest tumbleweed (zypper dup) and now chromium crashes
when called from the command line. Here is what I get:

~>[2072:2072:0207/150445.072560:ERROR:sandbox_linux.cc(364)]
InitializeSandbox() called with multiple threads in process gpu-process.
[2038:2038:0207/150446.384295:ERROR:x11_input_method_context_impl_gtk.cc(144)]
Not implemented reached in virtual void
libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const string16&,
const gfx::Range&)
Received signal 11 SEGV_MAPERR ffffc9dc77268269
#0 0x55f80c5abac1 base::debug::StackTrace::StackTrace()
#1 0x55f80c5aa4e3 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#2 0x55f80c5aba25 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7fb790f898f0 <unknown>
#4 0x7fb79031611b <unknown>
#5 0x7fb790316eb1 FcFontMatch
#6 0x55f80cfc9bf2 gfx::GetFontRenderParams()
#7 0x55f80af65e3e font_service::FontServiceApp::FontRenderStyleForStrike()
#8 0x55f809d1473b
font_service::mojom::FontServiceStubDispatch::AcceptWithResponder()
#9 0x55f80af64a1a font_service::mojom::FontServiceStub<>::AcceptWithResponder()
#10 0x55f80c60f497 mojo::InterfaceEndpointClient::HandleValidatedMessage()
#11 0x55f80c6137f0 mojo::internal::MultiplexRouter::ProcessIncomingMessage()
#12 0x55f80c616f8d mojo::internal::MultiplexRouter::Accept()
#13 0x55f80c60c3a3 mojo::Connector::ReadSingleMessage()
#14 0x55f80c60c9cb mojo::Connector::ReadAllAvailableMessages()
#15 0x55f80c629c2e mojo::SimpleWatcher::OnHandleReady()
#16 0x55f80c4f61b3 base::debug::TaskAnnotator::RunTask()
#17 0x55f80c574a74 base::internal::TaskTracker::RunOrSkipTask()
#18 0x55f80c5bd7e1 base::internal::TaskTrackerPosix::RunOrSkipTask()
#19 0x55f80c577234 base::internal::TaskTracker::RunAndPopNextTask()
#20 0x55f80c57104b base::internal::SchedulerWorker::RunWorker()
#21 0x55f80c5716c3 base::internal::SchedulerWorker::RunPooledWorker()
#22 0x55f80c5bd001 base::(anonymous namespace)::ThreadFunc()
#23 0x7fb790f7eed4 start_thread
#24 0x7fb78d814cbf __GI___clone
  r8: 000000000000001f  r9: 00007fb77f179460 r10: 000000000000002e r11:
0000000000000000
 r12: 00007fb7903315b5 r13: 0000362126d30b80 r14: 00007fb77f1795f8 r15:
00007fb77f1795f8
  di: 0000000000004278  si: 00007fb77f179460  bp: 00007fb77f179528  bx:
000000000000084f
  dx: 00007fb77f179460  ax: ffffc9dc77263ff1  cx: 00007fb77f179700  sp:
00007fb77f179410
  ip: 00007fb79031611b efl: 0000000000010246 cgf: 002b000000000033 erf:
0000000000000005
 trp: 000000000000000e msk: 0000000000000000 cr2: ffffc9dc77268269
[end of stack trace]
Calling _exit(1). Core file will not be generated.

>uname -a
Linux apersaud 4.20.6-1-default #1 SMP PREEMPT Thu Jan 31 07:37:50 UTC 2019
(463cfd2) x86_64 x86_64 x86_64 GNU/Linux

>cat os-release 
NAME="openSUSE Tumbleweed"
# VERSION="20190205"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20190205"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:tumbleweed:20190205"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"


I haven't noticed any other issues so far. Happy to provide more details if
needed or try out other suggestions.

Thanks


You are receiving this mail because: