I recently converted my notebook from Leap 15.1 to Tumbleweed (by the usual zypper dup procedure).
Only since then my Google Chrome (the default google-chrome-unstable, currently at 85.0.4186.2) reliably (always) crashes by either attaching or detaching a USB-C connected (HiDPI) external monitor or by hanging a monitor setup parameter (e.g. resolution or orientation) with KDE systemsettings5.
This happens even with only a single browser window on the notebook’s internal display.
As in this case the browser does not have to re-render any window contents to adapt to a new screen resolution, I imagine that the problem may lay in the interaction between the desktop environment (Plasma/KDE) and the browser in case of a changed monitor setup.
Unfortunately, this also happens when leaving the notebook unattended, supposedly due to the monitor going to power saving mode.
Thus, I’m going through a browser restart procedure more than twice a day (with this is only feasible for me by temporarily disconnecting from the network due to me having usually 250+ tabs in 50+ windows open). Since I heavily rely on this browser for my daily work, any help would be appreciated:
Can someone please confirm this Tumbleweed issue?
Or narrow in by changing the desktop layout with a dual-monitor setup with the more common full HD resolution?
Or give some advice how further to analyze the situation?
I narrowed this down to the following more simple (i.e. more broad and thus more severe) error conditions:
As already said, attaching/detaching an external monitor (or the monitor going into power saving mode) reliably (always) crashes the google-chrome browser (with the browser automatically reporting to Google).
I found that the problem can easily be tested in systemsettings5 by just changing a monitor setup parameter (resolution, orientation, etc.) triggering the crash.
It turns out that the problem also occurs in a single monitor setup (i.e. just my Thinkpad’s internal display)and regardless of how many browser windows are open.
Changing to a different OpenGL version of the compositor (in systemsettings5) has no effect on this behavior (and also does not trigger the crash on its own).
This problem does not occur with the Firefox browser or other applications.
As already said, the problem did not occur running up-to-date Leap 15.1.
Current software is Chrome 85.0 with Plasma 5.19 on Qt libs 5.15.
I.e. I’m running on a quite boring commodity hardware setup, i.e. standard Intel graphics and thus no problems due to non disclosed AMD or NVidia hardware “features” and Thinkpads are known to be quite Linux friendly.