[Bug 1225863] New: Chromium crashes on startup

https://bugzilla.suse.com/show_bug.cgi?id=1225863 Bug ID: 1225863 Summary: Chromium crashes on startup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: dev@dominik-schmidt.de QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- After updating openSUSE Tumbleweed the other day Chromium is now crashing for me on startup (i.e. I don't get to see a window at all). My system is completely up to date, I switched all packages from packman to repo-oss. When running Chromium in GDB I can retrieve this backtrace:
0x000055555e2ec853 in partition_alloc::internal::FreelistCorruptionDetected(unsigned long) () (gdb) bt #0 0x000055555e2ec853 in partition_alloc::internal::FreelistCorruptionDetected(unsigned long) () #1 0x000055555e2fc487 in allocator_shim::internal::PartitionMalloc(allocator_shim::AllocatorDispatch const*, unsigned long, void*) () #2 0x000055555dc170f2 in base::allocator::dispatcher::internal::DispatcherImpl<base::PoissonAllocationSampler>::AllocFn(allocator_shim::AllocatorDispatch const*, unsigned long, void*) () #3 0x000055555e2fba1b in malloc () #4 0x00007ffff36aa75e in strdup () at /lib64/libc.so.6 #5 0x00007ffff72a7439 in () at /lib64/libfontconfig.so.1 #6 0x00007ffff72a8f3c in () at /lib64/libfontconfig.so.1 #7 0x00007ffff72ad2c5 in () at /lib64/libfontconfig.so.1 #8 0x00007ffff71ce988 in () at /lib64/libexpat.so.1 #9 0x00007ffff71cb7c4 in () at /lib64/libexpat.so.1 #10 0x00007ffff71cdc49 in () at /lib64/libexpat.so.1 #11 0x00007ffff71c2258 in () at /lib64/libexpat.so.1 #12 0x00007ffff71ca3e5 in XML_ParseBuffer () at /lib64/libexpat.so.1 #13 0x00007ffff72a97d5 in () at /lib64/libfontconfig.so.1 #14 0x00007ffff72aa11e in () at /lib64/libfontconfig.so.1 #15 0x00007ffff72924ef in () at /lib64/libfontconfig.so.1 #16 0x00007ffff728d5b9 in () at /lib64/libfontconfig.so.1 #17 0x00007ffff72927d9 in FcInit () at /lib64/libfontconfig.so.1 #18 0x000055555f0e7a78 in base::NoDestructor<gfx::(anonymous namespace)::GlobalFontConfig>::NoDestructor<>() () #19 0x000055555f0e7a06 in base::internal::Invoker<base::internal::FunctorTraits<gfx::InitializeGlobalFontConfigAsync()::$_0&&>, base::internal::BindState<false, false, false, gfx::InitializeGlobalFontConfigAsync()::$_0>, void ()>::RunOnce(base::internal::BindStateBase*) () #20 0x000055555e236f4b in base::TaskAnnotator::RunTaskImpl(base::PendingTask&) () #21 0x000055555e25aef8 in base::internal::TaskTracker::RunTaskImpl(base::internal::Task&, base::TaskTraits const&, base::internal::TaskSource*, base::internal::SequenceToken const&) () #22 0x000055555e25afc1 in base::internal::TaskTracker::RunSkipOnShutdown(base::internal::Task&, base::TaskTraits const&, base::internal::TaskSource*, base::internal::SequenceToken const&) () #23 0x000055555e25abf3 in base::internal::TaskTracker::RunTask(base::internal::Task, base::internal::TaskSource*, base::TaskTraits const&) () #24 0x000055555e25a717 in base::internal::TaskTracker::RunAndPopNextTask(base::internal::RegisteredTaskSource) () #25 0x000055555e26d2df in base::internal::WorkerThread::RunWorker() () #26 0x000055555e26ceaa in base::internal::WorkerThread::RunPooledWorker() () #27 0x000055555e26cd2a in base::internal::WorkerThread::ThreadMain() () #28 0x000055555e28a08a in base::(anonymous namespace)::ThreadFunc(void*) () #29 0x00007ffff3692ba2 in start_thread () at /lib64/libc.so.6 #30 0x00007ffff371400c in clone3 () at /lib64/libc.so.6
I also tried 125.0.6422.141-1965.1-x86_64 from network:chromium/chromium, but it shows the same behavior. As it looks related to fontconfig, I ran
fc-cache -f -v as user and root with no success either.
Happy to provide any additional system information, logs, outputs... Thanks in advance -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1225863 https://bugzilla.suse.com/show_bug.cgi?id=1225863#c1 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Stieger@gmx.de, | |dev@dominik-schmidt.de, | |gmbr3@opensuse.org Flags| |needinfo?(dev@dominik-schmi | |dt.de) --- Comment #1 from Andreas Stieger <Andreas.Stieger@gmx.de> --- Do you remember the last working configuration? What can you tell me about the affected system? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1225863 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|Andreas.Stieger@gmx.de | -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1225863 Arrigo Marchiori <ardovm@yahoo.it> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ardovm@yahoo.it -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1225863 https://bugzilla.suse.com/show_bug.cgi?id=1225863#c8 --- Comment #8 from Arrigo Marchiori <ardovm@yahoo.it> --- Hello, I am writing about my experience in the hope it can be useful. I was seeing a similar bug (i.e. a crash in libfontconfig) on another, unlrelated software, after updating from Leap 15.5 to 15.6. Function FcInit() takes no parameters and should just work™. If it crashes, it must be due to something external to the calling software, like configuration files or environment variables. I forcibly reinstalled fontconfig RPM's and this somewhat fixed the issue. I noticed that some files in /etc/fonts were updated by the latest fontconfig installation. I tend to believe that a ``new'' fontconfig could crash on ``old'' configuration files. So a possible fix to this issue could consist of reinstalling fontconfig RPM's, in order to make sure that they move away (with the .rpmsave extension) outdated configuration files. Another (somewhat dangerous) test could consist of completely removing (i.e. renaming away) /etc/fonts and reinstalling fontconfig and all other packages so they recreate it. # zypper se --provides /etc/fonts could give a first idea of the relevant packages. Do it at your own risk. FWIW, chromium-125.0.6422.112-bp156.1.1.x86_64 is starting normally on my Leap 15.6, with fontconfig-2.14.2-150600.1.3.x86_64 I hope this helps. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com