Chromium menu is blank and freezes application

[Ward Louckx]

When opening the Chromium menu (3 dots button), it shows an empty blank white box. Very often it also freezes the whole application for about 10 seconds

Installed version:
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
  An open-source browser project that aims to build a safer, faster, and more stable way for all
  Internet users to experience the web.
commands:
  - chromium.chromedriver
  - chromium
snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
tracking: latest/stable
refresh-date: 6 days ago, at 08:45 EEST
channels:
  latest/stable: 90.0.4430.93 2021-04-28 (1568) 145MB -
  latest/candidate: 90.0.4430.93 2021-04-28 (1568) 145MB -
  latest/beta: 91.0.4472.19 2021-04-28 (1566) 148MB -
  latest/edge: 92.0.4496.0 2021-05-05 (1575) 148MB -
installed: 90.0.4430.93 (1568) 145MB -

Ubuntu version
Description: Ubuntu 21.04
Release: 21.04

DE: plasmashell 5.21.4

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michal Bachraty (m.bachraty)]

I have same problem, + it hangs when I click on <select> html items
It looks to be connected with GPU (I have AMD Ryzen 7 4750U CPU with Radeon graphics).
After chromium hangs, it took about 10 seconds to restart chromium. These log messages appears in console:

[120832:120832:1217/115511.669028:ERROR:command_buffer_proxy_impl.cc(328)] GPU state invalid after WaitForGetOffsetInRange.
[120832:120832:1217/115511.676066:ERROR:gpu_process_host.cc(967)] GPU process exited unexpectedly: exit_code=512
si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance counters)
[122614:122614:1217/115511.784632:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

When chromium app starts, this messages are shown:

si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance counters)
[120938:120938:1217/114538.723373:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[120832:120925:1217/114541.025791:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends.
[120832:120925:1217/114541.025815:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)] crbug.com/1216328: Checking Bluetooth availability ended.
[120832:120925:1217/114541.025819:ERROR:chrome_browser_main_extra_parts_metrics.cc(232)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends.
[120832:120965:1217/114541.072325:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration.
[120832:120925:1217/114541.155048:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)] crbug.com/1216328: Checking default browser status ended.
Warning: disabling flag --expose_wasm due to conflicting flags

Kernel: Linux 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Not installed AMD PRO drivers

Version:
Chromium 96.0.4664.110 (Official Build) snap (64-bit)
Revision d5ef0e8214bc14c9b5bbf69a1515e431394c62a6-refs/branch-heads/4664@{#1283}
OS Linux
JavaScript V8 9.6.180.21
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36
Command Line /snap/chromium/1854/usr/lib/chromium-browser/chrome --password-store --flag-switches-begin --flag-switches-end --origin-trial-disabled-features=CaptureHandle
Executable Path /snap/chromium/1854/usr/lib/chromium-browser/chrome
Profile Path /home/michal/snap/chromium/common/chromium/Default
Variations b56a9ab2-5558097f

[Pellaeon Lin (pellaeon)]

Hi, I have the same problem. Except for me the bug doesn't trigger with the upper-right 3-dot menu, rather, it triggers when I right click for the context menu in the dev tools, as well as regular HTML <select> elements in webpages.

When I right click for a context menu or left click on <select> elements, the whole chromium hangs. After around 10 seconds, the following message is printed on the console:
---
[1391245:7:0119/164748.438014:ERROR:command_buffer_proxy_impl.cc(328)] GPU state invalid after WaitForGetOffsetInRange.
[1387822:1387822:0119/164748.438696:ERROR:command_buffer_proxy_impl.cc(328)] GPU state invalid after WaitForGetOffsetInRange.
[1387822:1387822:0119/164748.475519:ERROR:gpu_process_host.cc(968)] GPU process exited unexpectedly: exit_code=512
si_init_perfcounters: max_sh_per_se = 2 not supported (inaccurate performance counters)
[1394246:1394246:0119/164748.562847:ERROR:sandbox_linux.cc(378)] InitializeSandbox() called with multiple threads in process gpu-process.
[1391305:7:0119/164748.596493:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
----

Desktop environment: KDE Plasma
Kernel: 5.13.0-23-generic #23-Ubuntu SMP Fri Nov 26 11:41:15 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Version: 97.0.4692.71
Rev: 1864

[Pellaeon Lin (pellaeon)]

I'm also using AMD graphics: AMD Ryzen 7 PRO 5850U with Radeon Graphics.

This bug also happens in the Snap version of Spotify, though the non-Snap version of Spotify works entirely fine.

[Olivier Tilloy (osomon)]

Possibly related: https://forum.snapcraft.io/t/some-snap-apps-no-longer-starting-up-on-amd-laptop/26403.

That post mentions that core20-based snaps aren't affected, and chromium was recently updated to core20. To anyone affected, can you please test again and let us know whether the problem is gone?

[Pellaeon Lin (pellaeon)]

I tested the latest chromium with core20 and can confirm that the problem is gone.

I also found a way to patch snaps that are not using core20: https://forum.snapcraft.io/t/how-to-patch-a-broken-snap-locally-changing-base/30596

(I guess there would be problems if one simply changes the base from core18 to core20 for many snaps due to different library versions, etc. Just that I got lucky with spotify.)