[Bug 287002] panel freezes

Sergio sergio.callegari at gmail.com
Sun Feb 19 12:18:32 GMT 2012


https://bugs.kde.org/show_bug.cgi?id=287002





--- Comment #96 from Sergio <sergio callegari gmail com>  2012-02-19 12:18:30 ---
Thanks for the link. That was interesting.

Just a couple of notes:

"With the numbers of daemons we need, but with the very little work they do, it
makes sense to use a single process for all of them. The key advantage is less
memory usage, and this is exactly what kded4, the KDE daemon process, exploits:
To enable the various daemon functionalities, it loads specialized kded modules
instead of needing a separate process for each of them."

Just out of curiosity. Isn't this exactly what linux threads with shared memory
(or lightweight processes) are about? Less memory use, yet avoiding the
cooperative approach where the probability of having a fault affecting all the
actors gets multiplied by the number of actors?

Apart from that, I still think that kded is buggy. The bug is in leaving the
user the responsibility of "Isolating the Offender" namely "find out which
module is responsible."  Kded should implement a timer and whenever a tasks
keeps control for too long (say 1 second) it should kill it and give a message
about a service that is buggy and needs disabling.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list