Bug#994278: Chromium freezes (rarely) and partially locks up my WM (xfce4)
On Sun, 16 Jan 2022 02:49:01 +1100 Craig Sanders wrote: > On Tue, Jan 11, 2022 at 03:33:21PM -0500, Andres Salomon wrote: > > On Wed, 15 Sep 2021 11:29:48 +1000 Craig Sanders wrote: > > > Package: chromium > > > Version: 90.0.4430.212-1 > > > Can you please tell me if you see this with chromium 97 or above? This > > sounds like a bug related to X11 API usage (ie, grabbing window focus and > > not letting go). We switched backends to ozone (which should be better > > supported), and I'm curious if it still occurs with ozone-x11. > > 97? Is that in experimental? Latest in sid is 93.0.4577.82-1 > > According to my /var/log/dpkg.log files, I upgraded to that on Sep 22 last > year, about a week after my bug report. > > I haven't seen it with this version yet, which is a good sign. It happened > infrequently anyway but I would have expected to see it at least once since > then. > It's been over a year, with a lot of new chromium releases (we're currently up to 110). I'm planning to close this, unless you've continued to see this bug with newer versions.
Bug#994278: Chromium freezes (rarely) and partially locks up my WM (xfce4)
On Sat, Jan 15, 2022 at 1:03 PM Craig Sanders wrote: > > On Tue, Jan 11, 2022 at 03:33:21PM -0500, Andres Salomon wrote: > > On Wed, 15 Sep 2021 11:29:48 +1000 Craig Sanders wrote: > > > Package: chromium > > > Version: 90.0.4430.212-1 > > > Can you please tell me if you see this with chromium 97 or above? This > > sounds like a bug related to X11 API usage (ie, grabbing window focus and > > not letting go). We switched backends to ozone (which should be better > > supported), and I'm curious if it still occurs with ozone-x11. > > 97? Is that in experimental? Latest in sid is 93.0.4577.82-1 No, this version (97) is in sid and stable-security now. 97.0.4692.71 is the current version. -- Cheers, Leandro Cunha
Bug#994278: Chromium freezes (rarely) and partially locks up my WM (xfce4)
On Tue, Jan 11, 2022 at 03:33:21PM -0500, Andres Salomon wrote: > On Wed, 15 Sep 2021 11:29:48 +1000 Craig Sanders wrote: > > Package: chromium > > Version: 90.0.4430.212-1 > Can you please tell me if you see this with chromium 97 or above? This > sounds like a bug related to X11 API usage (ie, grabbing window focus and > not letting go). We switched backends to ozone (which should be better > supported), and I'm curious if it still occurs with ozone-x11. 97? Is that in experimental? Latest in sid is 93.0.4577.82-1 According to my /var/log/dpkg.log files, I upgraded to that on Sep 22 last year, about a week after my bug report. I haven't seen it with this version yet, which is a good sign. It happened infrequently anyway but I would have expected to see it at least once since then. I'll need to check if 97 breaks any of my essential plugins (umatrix, ublock origin, stylus) before I upgrade to that. craig
Bug#994278: Chromium freezes (rarely) and partially locks up my WM (xfce4)
On Wed, 15 Sep 2021 11:29:48 +1000 Craig Sanders wrote: > Package: chromium > Version: 90.0.4430.212-1 > > I have no idea what causes this, but I've noticed it several times over the > last year or two, always while using unix.stackexchange.com "U" (so it's > probably got something to do with chromium's javascript interpreter). > > Anyway, while editing a post on U, chromium will sometimes lock up, no > longer responding to any keyboard or mouse input. When it does this, it > also locks up most user interface elements in XFCE (the xfce4-panel, menus, > buttons, tabs, etc). > > I can Alt-Tab to a terminal window to kill chromium, but if I click on a menu > (e.g. the File menu) in the terminal, I'm unable to either select a menu item > or get out of that menu...effectively freezing the terminal too. > > As soon as I kill chromium, xfce returns to normal behaviour. Restarting > chromium does NOT trigger the lockup again, even when the U page gets reload > by the chromium session manager (so, maybe some kind of memory or handle > leak??). > > This only happens very rarely - maybe once every few months. > Hi, Can you please tell me if you see this with chromium 97 or above? This sounds like a bug related to X11 API usage (ie, grabbing window focus and not letting go). We switched backends to ozone (which should be better supported), and I'm curious if it still occurs with ozone-x11. Thanks, Andres
Bug#994278: Chromium freezes (rarely) and partially locks up my WM (xfce4)
Package: chromium Version: 90.0.4430.212-1 I have no idea what causes this, but I've noticed it several times over the last year or two, always while using unix.stackexchange.com "U" (so it's probably got something to do with chromium's javascript interpreter). Anyway, while editing a post on U, chromium will sometimes lock up, no longer responding to any keyboard or mouse input. When it does this, it also locks up most user interface elements in XFCE (the xfce4-panel, menus, buttons, tabs, etc). I can Alt-Tab to a terminal window to kill chromium, but if I click on a menu (e.g. the File menu) in the terminal, I'm unable to either select a menu item or get out of that menu...effectively freezing the terminal too. As soon as I kill chromium, xfce returns to normal behaviour. Restarting chromium does NOT trigger the lockup again, even when the U page gets reload by the chromium session manager (so, maybe some kind of memory or handle leak??). This only happens very rarely - maybe once every few months. I don't know whether it does the same thing with other window managers/desktop environments. BTW, I tend to leave chromium running for days, weeks, or even months at a time and have dozens of windows with hundreds of tabs. I have Adblock Origin and uMatrix and several other extensions installed, but allow most js on stack exchange sites (they won't work without it). Sorry for the lack of details and the lack of any easy or consistent way to reproduce the bug. craig ps: a browser locking up isn't that big a deal to me, it's almost to be expected given the nature of the web and javascript...but locking up the WM too is a problem. I've rebooted my machine a few times due to this until I realised it was chromium doing it and that just killing chromium would "fix" it. -- craig sanders
