On Wed, Nov 30, 2022 at 10:36 AM Claudio Jeker <cje...@diehard.n-r-g.com> wrote: > > On Wed, Nov 30, 2022 at 02:47:41PM +0100, David Coppa wrote: > > Often, I'd say about half the attempts to start it, chromium shows me > > a blank window and nothing else. > > > > Chromium version is 107.0.5304.121 (latest one), but the same thing > > happened with previous versions as well (maybe less often?) > > Typical chrome issue. Kill the gpu-process for it to recover. > Using `pkill -f --type=gpu-process` is normally enough. Also if you wait > long enough chrome should do that automatically (since some time).
Thanks for this tip, Claudio! I have been experiencing this same issue with Chromium under Intel machines for years, but I've clearly never waited long enough for it to self-recover. I have confirmed that killing the gpu-process works for `chrome` and `iridium` under amd64/7.2-stable, though I'll note that the command does need an additional delimiter to prevent an "unknown option" error: `pkill -f -- --type=gpu-process`. Morgan
