Public bug reported:

Chromium can freeze the entire X11 graphical desktop when opening
certain native HTML <select> dropdowns. The issue is reproducible on a
public MDN page as well as in a separate authenticated web application.

Environment
-----------
Ubuntu: 24.04.5 LTS
Architecture: x86_64
Kernel: 6.8.0-146-generic
Session: X11/Xorg
Desktop: MATE 1.26.2 / Marco
Chromium: 154.0.8037.57, snap revision 3548, latest/stable
GPU: NVIDIA GeForce GTX 1050 (GP107, 2 GB)
NVIDIA driver: 580.178.04 proprietary
OpenGL renderer: NVIDIA GeForce GTX 1050/PCIe/SSE2
Displays: two

Steps to reproduce
------------------
1. Start an X11 MATE session.
2. Start Chromium normally with GPU acceleration enabled.
3. Open:
   https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/select
4. Interact with a native HTML <select> dropdown on the page.
5. The graphical desktop can become unresponsive.

The same problem is also reproducible in a separate authenticated web
application when opening a native HTML <select> dropdown there.

Expected result
---------------
The dropdown opens normally, a selection can be made, and Chromium and the 
desktop remain responsive.

Actual result
-------------
Opening the affected <select> dropdown can freeze Chromium and the graphical 
X11 desktop.

During controlled tests, background diagnostics continued running while
the graphical session was unresponsive. Recovery required terminating
Chromium from a previously scheduled background process or otherwise
recovering/restarting the session.

Important isolation results
---------------------------
- A small local HTML page containing an ordinary three-option <select> did NOT 
reproduce the problem, with either a fresh or existing Chromium profile.
- The public MDN <select> page DOES reproduce the problem.
- The authenticated application also reproduces the problem.
- Starting Chromium with --disable-gpu-compositing does NOT prevent the freeze.
- Disabling Marco compositing does NOT prevent the freeze.
- Starting Chromium with --disable-features=Vulkan prevents the freeze in 
repeated testing of the affected application.
- Chromium still uses the GPU process with Vulkan disabled, so this workaround 
does not simply disable all hardware acceleration.

Working workaround
------------------
The following command has allowed repeated use of the affected select without 
freezing:

chromium --disable-features=Vulkan,TFLiteLanguageDetectionEnabled

TFLiteLanguageDetectionEnabled was already disabled by the installed
snap launcher; Vulkan is the relevant difference found during testing.

Diagnostics
-----------
No NVIDIA Xid errors were found in the captured kernel logs around the freeze.

No OOM kill or obvious Chromium segfault was observed.

During the freeze, Chromium renderer stacks showed activity/waits in
paths including:

- libGLESv2.so
- libvulkan.so.1
- libX11.so
- libxcb.so
- poll()
- futex_wait()

Chromium stderr also contained renderer tile-memory warnings such as:

WARNING:cc/tiles/tile_manager.cc
"Some frames with checkerboarding are likely"

A GBM permission warning was observed as well, but it also appeared
during non-freezing control runs, so it does not appear sufficient to
explain the freeze by itself.

Scope / interpretation
----------------------
This does not appear to be specific to the authenticated application, because 
it can also be reproduced on the public MDN <select> reference page.

However, not every HTML <select> triggers the problem: a minimal local
three-option select did not reproduce it. The exact
page/content/rendering condition still needs reduction.

The strongest isolation result so far is that disabling Chromium's
Vulkan feature prevents the freeze, whereas disabling GPU compositing or
the Marco compositor does not.

This suggests a Chromium graphics/popup rendering interaction involving
the Vulkan path on X11 with the proprietary NVIDIA driver, but the exact
responsible component has not been established.

Possibly related
----------------
Launchpad #2122731 also reports whole-desktop freezes involving Chromium 
graphics, but that report differs significantly: it is primarily triggered at 
Chromium startup and includes Wayland/AMD cases. This report occurs on 
X11/NVIDIA and is triggered specifically by opening certain native HTML 
<select> dropdowns.

Additional diagnostic logs and controlled test results are available and
can be attached if useful.

** Affects: chromium-browser (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "env_details.txt"
   
https://bugs.launchpad.net/bugs/2169544/+attachment/6005812/+files/env_details.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169544

Title:
  Chromium freezes the X11 desktop when opening some HTML select
  dropdowns with NVIDIA/Vulkan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2169544/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to