Bug 1225863

Summary:	Chromium crashes on startup
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Dominik Schmidt <dev>
Component:	Network	Assignee:	Callum Farmer <gmbr3>
Status:	NEW ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	Andreas.Stieger, dev, gmbr3, santiago.zarate
Version:	Current	Flags:	Andreas.Stieger: needinfo? (dev)
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE Tumbleweed
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	log on wayland log on x11

Description Dominik Schmidt 2024-06-03 16:12:16 UTC

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

Comment 1 Andreas Stieger 2024-06-03 18:17:54 UTC

Do you remember the last working configuration?
What can you tell me about the affected system?

Comment 2 Dominik Schmidt 2024-06-04 09:09:36 UTC

Not much unfortunately, I don't know which version I upgraded from - it's been a while since I did a full zypper dup, I *think* it might be 3 months or so.

I'm running KDE/Plasma 6.2.0 on Qt 6.7 - I think I switched from KDE/Qt 5 with this update - no idea if that's related.

Please let me know what other information might be relevant, I'm pretty clueless here.

If there's an easy way to test older versions of Chromium, I'm happy to do that as well. The leap packages (unsurprisingly) are not installable because of dependency issues and older Tumbleweed packages are not available on the mirrors anymore, right?

Comment 3 Dominik Schmidt 2024-06-04 09:17:03 UTC

... and for what it's worth: it happens on Wayland and X11.

Comment 4 Callum Farmer 2024-06-04 10:52:51 UTC

Try:
chromium-browser --enable-logging=stderr --v=1 > log.txt 2>&1

Then:
Upload the log.txt file

Comment 5 Dominik Schmidt 2024-06-04 10:56:54 UTC

Created attachment 875295 [details]
log on wayland

Comment 6 Dominik Schmidt 2024-06-04 10:57:10 UTC

Created attachment 875296 [details]
log on x11

Comment 7 Dominik Schmidt 2024-06-04 10:58:34 UTC

Added logs - look pretty similar (if not identical) on x11 and wayland, but I saw the x11_display_manager.cc messages and thought it won't hurt to post both.