Date: Sun, 10 Sep 2023 03:47:37 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 273669] x11/kde5: kde5 opens too many files and freezes the system (with disabled Baloo) - KDE is unusable when the home directory has a lot of files Message-ID: <bug-273669-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273669 Bug ID: 273669 Summary: x11/kde5: kde5 opens too many files and freezes the system (with disabled Baloo) - KDE is unusable when the home directory has a lot of files Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: kde@FreeBSD.org Reporter: yuri@freebsd.org Assignee: kde@FreeBSD.org Flags: maintainer-feedback?(kde@FreeBSD.org) KDE5 works fine when the home directory doesn't have too many files. Baloo causes this type of problem, but 'balooctl status' says that baloo is disabled, so something else opens too many files. But on my system the home directory has a lot of files and KDE runs out of = file descriptors. kern.maxfiles can be increased, of course, but it is obviously a bad idea to open every available file, and this definitely would cause performance issu= es when kern.maxfiles would be sufficiently large. The dmesg log looks like this: kern.maxfiles limit exceeded by uid 1001, (dolphin) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (plasmashell) please see tuning(7= ). kern.maxfiles limit exceeded by uid 1015, (date) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (DiscoverNotifier) please see tuning(7). kern.maxfiles limit exceeded by uid 1015, (date) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (kgpg) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (DiscoverNotifier) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (chrome) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (chrome) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (chrome) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (plasmashell) please see tuning(7= ). kern.maxfiles limit exceeded by uid 1001, (DiscoverNotifier) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (kwin_killer_helper) please see tuning(7). pid 94202 (kwin_killer_helper), jid 0, uid 1001: exited on signal 5 kern.maxfiles limit exceeded by uid 1001, (kwin_killer_helper) please see tuning(7). pid 94204 (kwin_killer_helper), jid 0, uid 1001: exited on signal 5 kern.maxfiles limit exceeded by uid 1001, (DiscoverNotifier) please see tuning(7). kern.maxfiles limit exceeded by uid 1015, (date) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (qtox) please see tuning(7). kern.maxfiles limit exceeded by uid 1015, (date) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (kgpg) please see tuning(7). kern.maxfiles limit exceeded by uid 1015, (date) please see tuning(7). kern.maxfiles limit exceeded by uid 1001, (plasmashell) please see tuning(7= ). kern.maxfiles limit exceeded by uid 1015, (sh) please see tuning(7). kern.maxfiles limit exceeded by uid 1015, (sleep) please see tuning(7). kern.maxfiles limit exceeded by uid 1015, (sleep) please see tuning(7). kern.maxfiles limit exceeded by uid 1015, (sleep) please see tuning(7). pid 93733 (firefox), jid 0, uid 1001: exited on signal 11 kern.maxfiles limit exceeded by uid 1001, (firefox) please see tuning(7). pid 8573 (firefox), jid 0, uid 1001: exited on signal 11 kern.maxfiles limit exceeded by uid 1001, (firefox) please see tuning(7). pid 8611 (firefox), jid 0, uid 1001: exited on signal 11 pid 8604 (firefox), jid 0, uid 1001: exited on signal 11 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273669-7788>