Google-chrome (dnf) and ungoogled_chromium (flatpak) won't start

Edit

Also facing issues with chromium based products: Vscode, Codium

Info

Installed kernel: 6.12.11-200.fc41.x86_64
Fedora 41
Gnome
Wayland

$ google-chrome --version
Google Chrome 133.0.6943.98 
$ flatpak run io.github.ungoogled_software.ungoogled_chromium --version
Ungoogled Chromium 133.0.6943.53 

Issue

google-chrome was working fine until 2 days ago, both starting with CLI or with Gnome GUI.

After the latest full system update of Fedora (2 days ago), google-chrome and ungoogled_chromium, simply won’t start. Running, google-chrome and flatpak run io.github.ungoogled_software.ungoogled_chromium on CLI gives no output, except:

$ flatpak run io.github.ungoogled_software.ungoogled_chromium
Gtk-Message: 07:48:08.446: Failed to load module "pk-gtk-module"
Gtk-Message: 07:48:08.447: Failed to load module "pk-gtk-module"

Log

Install

sudo dnf install -y google-chrome-stable
flatpak run io.github.ungoogled_software.ungoogled_chromium

Steps taken

  • shutdown and reboot
  • uninstalled google-chrome and installed again
  • deleted /mnt/Data/.config/google-chrome and forced it to be recreated

The log shows it quits (signal 5) abnormally, closest related to chromium and sigtrap that I can find is this Troubleshooting - SIGTAP — Kasm 1.16.1 documentation
But I’m assuming out of memory is not an issue on your system?
It’d be interesting to see if Brave (also Chromium based) would crash in the same way.

Does downgrading chromium give you a working version?

I have 32 GB DDR4 RAM, usually my maximum RAM consumption is 9 GB with all my usual applications running. I did observe in past few days (≈ a week) RAM usage increasing with time (in a span of a day or may be 8 hrs), and completely filling up and everything would freeze, sometimes Gnome would force close lot of GUI apps. Also I observed that excessive RAM usage would drop to normal, when I close Firefox manually.

May be Firefox or one of the extensions are behaving not appropriately (memory leak?)

Then after 3 days of that problem chromium (or electron?) based products won’t start at all, randomly. It was weird that when this problem occurs, sometimes the problem persisted even after a complete shutdown. But this should not happen as memory would take several hours to fill up, due to memory leak.

Electron is based (iirc) on a stripped down chromium engine.
You can check out of memory instances in your logs, look for ‘oom-killer’ and related terms.
For Firefox, consider tab suspender extensions.
But none of these are the actual (still unknown) cause.
Did downgrading chromium help?

I am not sure how can I do that.

For example google chrome was installed by downloading rpm file from the website. Vscode was installed using dnf, ungoogled-chromium was installed using flatpak.