Re: Chrome interferes with KDE
On Tuesday October 04 2022 15:36:07 Jerome wrote: >I keep about 20 tabs open across 2 Chrome windows, which doesn't seem like >much Indeed, I have more tabs in more Waterfox windows open. >The Marvellous Suspender will free up RAM, but not X connections. Not just RAM (plus evidently CPU cycles). Your Chrome session counted for more connections to the X server than the number of tab you have open, right? It's very likely that complex pages open multiple connections, for things like overlays, different compositing contexts etc. Before discovering The Great Suspender I would use Chrome's process manager to kill CPU and/or RAM hungry tabs without closing them; TSM works in a very similar way. The process corresponding to the page is killed, and the page replaced with something very simple; I have to assume this also means all "extraneous" connections to the X server are terminated (the ones in the browser process which keeps running; the ones in the killed process are released by definition). R.
Re: Chrome interferes with KDE
On Tuesday, October 4, 2022 3:17:08 P.M. MDT René J.V. Bertin wrote: > On Tuesday October 04 2022 15:00:28 Jerome wrote: > >> After 70 days of uptime, Chrome (prior and latest version) is interfering > > > >Closing enough things (like KWrite windows) to get Xorg to 255 or less > >clears the problem while I wait for a good time to log out/in again. > > Have you tried restarting Chrome (and a tab unloader like The Marvellous > Suspender, if you keep as many tabs open as I think you must do)? > > This must be about open files (and AFAIK sockets count to that number) and > it wouldn't surprise me at all that something as complex as Chrome doesn't > release all its connections to the X server perfectly as soon as they're no > longer needed. I could just fiddle with that, but now that I know it's a maxclients deficiency, and how to find how many X is using, I'm going to double the number until the next time I hit the limit. For now, until I restart X with a larger limit, I know what I'm looking for and how to deal with it. I keep about 20 tabs open across 2 Chrome windows, which doesn't seem like much, but I also keep other things open, like KWrite windows I use for scratchpads, and they all take X connections. The Marvellous Suspender will free up RAM, but not X connections. I have 32G of RAM so that's not a problem.
Re: Chrome interferes with KDE
On Tuesday October 04 2022 15:00:28 Jerome wrote: >> After 70 days of uptime, Chrome (prior and latest version) is interfering >Closing enough things (like KWrite windows) to get Xorg to 255 or less clears >the problem while I wait for a good time to log out/in again. Have you tried restarting Chrome (and a tab unloader like The Marvellous Suspender, if you keep as many tabs open as I think you must do)? This must be about open files (and AFAIK sockets count to that number) and it wouldn't surprise me at all that something as complex as Chrome doesn't release all its connections to the X server perfectly as soon as they're no longer needed. R.
Re: Chrome interferes with KDE
On Sunday, October 2, 2022 1:12:39 P.M. MDT Jerome wrote: > [Fedora 34] > > After 70 days of uptime, Chrome (prior and latest version) is interfering > with: > > - opening apps from the QuickLaunch panel > - opening Gwenview from a KMail link to an image > - Ctrl-Esc for System Activity > > When Chrome ISN'T open - all these work. > > When Chrome IS open: > > - nothing opens from QuickLaunch, or the requested app (eg: KWrite) > coredumps - Gwenview crashes > - Ctrll-Esc doesn't open System Activity > > I've done a plasmashell --restart & and that hasn't made a difference. > > Has anyone seen this behaviour before? A follow-up: I tried running kompare from a konsole and get this: Maximum number of clients reachedqt.qpa.xcb: could not connect to display :0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland- xcomposite-glx, xcb. Aborted (core dumped) So I Googled for "Maximum number of clients reached qt.qpa.xcb" and found Xorg has a default of 256, apparently hard-coded into the source. Two example results: https://www.reddit.com/r/archlinux/comments/u0095w/ dealing_with_an_issue_that_often_happens_after/ https://unix.stackexchange.com/questions/368017/cant-start-applications-due-to-maximum-number-of-clients-reached-error The solution seems to be to start X with a larger --maxclients with /etc/X11/xorg.conf.d/99-maxclients.conf: Section "ServerFlags" Option "MaxClients" "512" EndSection Which I am about to try. In testing with lsof -U +c 15 | cut -f1 -d' ' | sort | uniq -c | sort -rn | head -3 381 chrome 255 Xorg 180 kded5 Closing enough things (like KWrite windows) to get Xorg to 255 or less clears the problem while I wait for a good time to log out/in again.
Re: Chrome interferes with KDE
On Sunday October 02 2022 17:12:58 Jerome wrote: >to somewhere else. Reboot tomorrow morning I guess... 70 days is doing pretty >well for KDE 4... Fedora is still providing a KDE 4 desktop?? My FranKubunto 14.04 with Plasma4 desktop but self-built, parallel-installed KF5 versions of my main KDE apps is now at 69 days uptime. I don't use GChrome; the only reasons for reboots are either because it's about as fast as logging off and back in and will really free all resources, or because a pm-sleep doesn't complete and I have to power-cycle. R
Re: Chrome interferes with KDE
On Sunday, October 2, 2022 2:27:31 P.M. MDT Martin van Es wrote: > I have seen some weird stuff with Chrome and Plasma lately as well, but > they come and go with reboots and/or newer versions. > The global desktop stealing bug still happens now and then e.g. > > https://bugs.chromium.org/p/chromium/issues/detail?id=1342862 > https://bugs.chromium.org/p/chromium/issues/detail?id=1339788 > > It may be important to know that I use Wayland. I haven't seen that because I don't use it, but I've gotten used to needing to reboot for something Chrome does to some part of KDE. Pre-Fedora 34 I'd get about a month of uptime and Chrome would lock up everything on some trivial action. I thought F34 would fix that, but it seems to have moved the weirdness to somewhere else. Reboot tomorrow morning I guess... 70 days is doing pretty well for KDE 4... > On Sun, Oct 2, 2022 at 9:13 PM Jerome wrote: > > [Fedora 34] > > > > After 70 days of uptime, Chrome (prior and latest version) is interfering > > with: > > > > - opening apps from the QuickLaunch panel > > - opening Gwenview from a KMail link to an image > > - Ctrl-Esc for System Activity > > > > When Chrome ISN'T open - all these work. > > > > When Chrome IS open: > > > > - nothing opens from QuickLaunch, or the requested app (eg: KWrite) > > coredumps > > - Gwenview crashes > > - Ctrll-Esc doesn't open System Activity > > > > I've done a plasmashell --restart & and that hasn't made a difference. > > > > Has anyone seen this behaviour before?
Re: Chrome interferes with KDE
I have seen some weird stuff with Chrome and Plasma lately as well, but they come and go with reboots and/or newer versions. The global desktop stealing bug still happens now and then e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=1342862 https://bugs.chromium.org/p/chromium/issues/detail?id=1339788 It may be important to know that I use Wayland. On Sun, Oct 2, 2022 at 9:13 PM Jerome wrote: > [Fedora 34] > > After 70 days of uptime, Chrome (prior and latest version) is interfering > with: > > - opening apps from the QuickLaunch panel > - opening Gwenview from a KMail link to an image > - Ctrl-Esc for System Activity > > When Chrome ISN'T open - all these work. > > When Chrome IS open: > > - nothing opens from QuickLaunch, or the requested app (eg: KWrite) > coredumps > - Gwenview crashes > - Ctrll-Esc doesn't open System Activity > > I've done a plasmashell --restart & and that hasn't made a difference. > > Has anyone seen this behaviour before? > > > > -- If 'but' was any useful, it would be a logic operator
Chrome interferes with KDE
[Fedora 34] After 70 days of uptime, Chrome (prior and latest version) is interfering with: - opening apps from the QuickLaunch panel - opening Gwenview from a KMail link to an image - Ctrl-Esc for System Activity When Chrome ISN'T open - all these work. When Chrome IS open: - nothing opens from QuickLaunch, or the requested app (eg: KWrite) coredumps - Gwenview crashes - Ctrll-Esc doesn't open System Activity I've done a plasmashell --restart & and that hasn't made a difference. Has anyone seen this behaviour before?
