In my case I wasted time on debugging the issue, but it seems like there was just some issue on Linux with Wayland and Chrome. By default Chrome uses X11 instead of Wayland as Ozone platform. You can switch to Ozone platform auto and see if the issue persists. See chrome://flags/#ozone-platform-hint