Firefox crash in Tumbleweed snapshot 20260625

English Applications
1

Hello. I’ve updated to the latest snapshot, 20260625, and Firefox crashes on launch, with the amount of RAM used increasing significantly at intervals of about 5 seconds until the Firefox process is closed.
Launching the programme via the command line does not produce any error messages.
Best regards

CPU:
  Info: 6-core model: AMD Ryzen 5 6600H with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 3 MiB
  Speed (MHz): avg: 1395 min/max: 413/4566 cores: 1: 1395 2: 1395 3: 1395
    4: 1395 5: 1395 6: 1395 7: 1395 8: 1395 9: 1395 10: 1395 11: 1395 12: 1395
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M]
    driver: amdgpu v: kernel
  Display: wayland server: Xwayland v: 24.1.11 compositor: gnome-shell
    driver: gpu: amdgpu resolution: no compositor data resolution: 1920x1080
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.3 renderer: AMD Radeon 660M
    (radeonsi rembrandt ACO DRM 3.64 7.0.12-1-default)
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xprop
2

@Vernius I don’t run Firefox or any AMD hardware, but do use GNOME. Why no Vulkan present in the output? It’s better to use inxi -GSaz and show that output.

1 Like
3

Everything normal here on Intel+Nvidia, so possibly something HW related?

4

Can’t reproduce here. Firefox (and Librewolf) are running as expected.

─❯ kinfo
Operating System: openSUSE Tumbleweed 20260625
KDE Plasma Version: 6.7.1
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Memory: 32 GiB of RAM (30.6 GiB usable)
Graphics Processor: AMD Radeon Graphics
─❯
5

No FF issues here.

knurpht@Lenovo-P16:~> kinfo
kinfo        kinfocenter  
knurpht@Lenovo-P16:~> kinfo
Operating System: openSUSE Tumbleweed 20260625
KDE Plasma Version: 6.7.1
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics
Memory: 64 GiB of RAM (58.6 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
knurpht@Lenovo-P16:~>
1 Like
6

Hi, you’re right, that combination is better for Inxi. I’ve been running some tests and the issue occurs on both the laptop and the mini PC, both of which have AMD processors.
In both cases, the error occurs when I log in to my Mozilla account.

 Desktop: GNOME v: 50.2 tk: GTK v: 3.24.52 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 50.1 Distro: openSUSE Tumbleweed
    20260625
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M]
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, Writeback-1
    bus-ID: 75:00.0 chip-ID: 1002:1681 class-ID: 0300 temp: 42.0 C
  Display: wayland server: Xwayland v: 24.1.11 compositor: gnome-shell
    driver: gpu: amdgpu display-ID: 0
  Monitor-1: HDMI-A-1 model: Philips PHL 243V7 serial: <filter> built: 2023
    res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65")
    diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.3 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon 660M (radeonsi rembrandt ACO DRM
    3.64 7.0.12-1-default) device-ID: 1002:1681 memory: 2.93 GiB unified: yes
    display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xprop

Captura desde 2026-06-27 18-03-31
Captura desde 2026-06-27 18-03-313072×1664 72.2 KB

7

Where does your Mesa related packages from? Is packman involved?

8

Hello. I haven’t added the Packman repository to my installation

9

  1. Does the issue happen if you login using “X11” vs “wayland”?

  2. And another easy troubleshooting step is to create a brand new user account (never used before) … then logout of your regular user account, then login as the new user … does issue still happen?

10

Did you rule out the influence of Firefox extensions? You can test with Firefox safe mode/troubleshoot mode:
https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode

11

the same on a fresh install of tumbleweed

12

Hello. The Firefox application does not respond in any of the scenarios I’ve tested, whether or not extensions are enabled. It only works after restoring the session or on the first launch. For now, I’ve installed the Flatpak package, but I’m still testing with the native OpenSUSE package.
When Firefox starts up, the CPU load increases significantly, and RAM usage gradually rises until it reaches its maximum.
In BTOP, the open process that increases CPU load and RAM usage is the one called Firefox

Tumbleweed Gnome

13

@Vernius is the libvulkan_radeon package installed? You also didn’t post the full output of inxi -GSaz which shows additional information?

1 Like
14

The issue will probably be fixed with Firefox 152.0.3, e.g., from https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/

1 Like
15

Hello @malcolmlewis. The libvulkan_radeon package is indeed installed. The full output of inxi -GSaz is as follows (I’ve redacted part of the disk ID):

System:
  Kernel: 7.0.12-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: initrd=\opensuse-tumbleweed\7.0.12-1-default\initrd-89cd8a935bcbdd1526fe2**************
    root=UUID=056d308b-5712-4fcd-b01e-300d976a********  splash=silent
    resume=/dev/disk/by-uuid/25de0dc0-15ec-4150-9cec***********
    mitigations=auto quiet security=selinux selinux=1
    rootflags=subvol=@/.snapshots/1/snapshot
  Desktop: GNOME v: 50.2 tk: GTK v: 3.24.52 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 50.1 Distro: openSUSE Tumbleweed
    20260625
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M]
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, Writeback-1
    bus-ID: 75:00.0 chip-ID: 1002:1681 class-ID: 0300 temp: 43.0 C
  Display: wayland server: Xwayland v: 24.1.11 compositor: gnome-shell
    driver: gpu: amdgpu display-ID: 0
  Monitor-1: HDMI-A-1 model: Philips PHL 243V7 serial: <filter> built: 2023
    res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65")
    diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.3 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon 660M (radeonsi rembrandt ACO DRM
    3.64 7.0.12-1-default) device-ID: 1002:1681 memory: 2.93 GiB unified: yes
    display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: glxinfo x11: xprop

PD.: For now, I’m going to use Firefox from Flathub; until next weekend, I won’t have much time to do any more testing

16

@Vernius many apps use vulkan these days, but don’t see that in the output which is strange… is vulkan-tools installed?

Edit: What does the output from zypper se -i radeon vulkan egl show?

1 Like
17

Output of zypper se -i radeon vulkan

Loading repository data...
Reading installed packages...

S  | Name                      | Summary                                     | Type
---+---------------------------+---------------------------------------------+--------
i  | kernel-firmware-radeon    | Kernel firmware files for Radeon graphics-> | package
i  | libgstvulkan-1_0-0        | GStreamer Streaming-Media Framework Plug--> | package
i  | libvulkan1                | The Vulkan 3D graphics and compute API      | package
i  | libvulkan_lvp             | Mesa vulkan driver for LVP                  | package
i  | libvulkan_radeon          | Mesa vulkan driver for AMD GPU              | package
i  | Mesa-vulkan-anti-lag      | Vulkan layer to reduce the latency betwee-> | package
i  | Mesa-vulkan-device-select | Vulkan layer to select Vulkan devices pro-> | package

I have the installation that Yast performs by default

18

@Vernius I did edit my post and added egl, but install vulkan-tools.

1 Like
19 
~ ❯❯❯ LANG=C zypper se -i radeon vulkan egl
Loading repository data...
Reading installed packages...

S  | Name                        | Summary                                         | Type
---+-----------------------------+-------------------------------------------------+--------
i  | gegl-0_4                    | Generic Graphics Library                        | package
i  | gegl-0_4-lang               | Translations for package gegl-0_4               | package
i  | kernel-firmware-radeon      | Kernel firmware files for Radeon graphics dri-> | package
i  | libgegl-0_4-0               | Generic Graphics Library                        | package
i  | libgstvulkan-1_0-0          | GStreamer Streaming-Media Framework Plug-Ins    | package
i  | libvulkan1                  | The Vulkan 3D graphics and compute API          | package
i  | libvulkan_lvp               | Mesa vulkan driver for LVP                      | package
i  | libvulkan_radeon            | Mesa vulkan driver for AMD GPU                  | package
i  | libwayland-egl1             | Additional egl functions for wayland            | package
i  | Mesa-libEGL1                | EGL API implementation                          | package
i  | Mesa-vulkan-anti-lag        | Vulkan layer to reduce the latency between in-> | package
i  | Mesa-vulkan-device-select   | Vulkan layer to select Vulkan devices provide-> | package
i  | typelib-1_0-Gegl-0_4        | Introspection bindings for the GEGL "Generic -> | package
i  | typelib-1_0-GeocodeGlib-2_0 | Introspection bindings for geocode-glib         | package
20

@Vernius so install Mesa-demo-egl and vulkan-tools also update inxi by running inxi -U as root user. Then post the output from inxi -Gxxz

1 Like