Dear Maintainer, After upgrading Chromium on Debian 13 (Trixie, stable) from 139.0.7258.154-1~deb13u1 to 141.0.7390.65-1~deb13u1, starting Chromium immediately causes a complete system hang. The workstation becomes entirely unresponsive and requires a hard reboot. This behavior is new in the latest version and does not occur with the previous version. System details: - Debian 13 Trixie (stable) - Kernel: 6.12.48+deb13-amd64 - GPU: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270], using `radeon` driver - Mesa: 25.0.7-2 (libegl-mesa0, libgl1-mesa-dri, mesa-vulkan-drivers, etc.) Steps to reproduce: 1. Install chromium 141.0.7390.65-1~deb13u1 from trixie-security. 2. Launch chromium. 3. Whole system freezes, requires hard reset. Workarounds: - Downgrading to chromium 139.0.7258.154-1~deb13u1 resolves the issue. - With the older version the system is stable. This seems to be a regression introduced between Chromium 139.x and 141.x. Thank you for your work on maintaining Chromium in Debian. Best regards,
Hi, This is likely a bug related to your GPU. Please run chromium 141 with the '--disable-gpu' option and to see if that keeps it from crashing. Thanks, Andres
Hi Andreas,
this very same bug does not only affect chromium but all
V8/node.js-based apps.
`--disable-gpu` indeed does the trick, so your assumption seems true.
on my desktop computer it is present:
```
$ inxi --graphics
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Redwood PRO [Radeon HD
5550/5570/5630/6510/6610/7570] driver: radeon v: kernel
Device-2: Microdia USB Live camera driver: snd-usb-audio,uvcvideo
type: USB
Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
compositor: gnome-shell v: 48.5 driver: X: loaded: vesa
unloaded: fbdev,modesetting,radeon gpu: radeon resolution:
2560x1440~60Hz
API: EGL v: 1.5 drivers: kms_swrast,r600,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 25.2.5-1 renderer: AMD REDWOOD (DRM
2.50.0 / 6.16.12+deb14+1-amd64 LLVM 19.1.7)
API: Vulkan v: 1.4.321 drivers: llvmpipe surfaces: N/A
Info: Tools: api: eglinfo, glxinfo, vulkaninfo wl: wayland-info
x11: xdriinfo, xdpyinfo, xprop, xrandr
```
on my laptop chrome works fine:
```
# inxi --graphics
Graphics:
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v:
kernel
Device-2: Chicony HD WebCam driver: uvcvideo type: USB
Display: unspecified server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8
driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
resolution: 2560x1600~60Hz
API: EGL v: 1.5 drivers: iris,swrast platforms:
gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.2.5-1
renderer: Mesa Intel Iris Xe Graphics (TGL GT2)
Info: Tools: api: eglinfo,glxinfo wl: kanshi,wayland-info x11: xdriinfo,
xdpyinfo, xprop, xrandr
```
regards
Martin
On Sat, 11 Oct 2025 15:23:48 -0400 Andres Salomon <dilinger@queued.net> wrote:
------------------------------------------------------------------------
Thanks for the feedback, everyone. Can you please tell me if this problem still occurs on chromium 143.0.7499.109?
Hi Franz, Unfortunately your mail provider has blocked my mail server, but please see the followup on the bug. Thanks, Andres
Hi,
AMD GPU as well.
```
inxi --graphics
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Cape Verde PRO [Radeon HD
7750/8740 / R7 250E] driver: radeon v: kernel
Display: wayland server: X.Org v: 24.1.9 with: Xwayland v: 24.1.9
compositor: gnome-shell v: 49.2 driver: X: loaded: fbdev,modesetting,vesa
dri: radeonsi gpu: radeon resolution: 2560x1440~60Hz
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: amd mesa v: 25.3.2-2 renderer: VERDE (radeonsi
ACO DRM 2.51 6.17.13+deb14-amd64)
API: Vulkan Message: No Vulkan data available.
Info: Tools: api: eglinfo, glxinfo, vulkaninfo gpu: radeontop wl: swaymsg
x11: xdriinfo, xdpyinfo, xprop, xrandr
```
With 143.0.7499.169 my system doesn't freeze anymore immediately, when I run
chromium. But I have a lot of graphical artifacts, when chromium is
running on Wayland with GPU acceleration.
Probably this is upstream issue: https://issues.chromium.org/issues/470919961
Since this is specific to a certain GPU and happens with a non-default setting (ozone-platform set to wayland instead of auto or x11), I'm lowering the severity. Please follow up when this ends up getting fixed with your GPU in wayland.