Right now I don't have any memory leak, but any add-on can leak memory into the plasmashell process.
So when there is going to be a leak cannot be controlled in reality. Even if you want to fix it, the consequences of not having a safeguard is a critical system failure. Anyway I will contact them. Thanks 👍 On Tue, 16 Mar 2021 at 15:39, Konstantin Kharlamov <[email protected]> wrote: > I think the most interesting thing here is to know what plasmashell > developers > think about it. Is it perhaps possible they don't have a reproducer for > memory > leak, and you have it? In which case it seems more productive to fix the > bug. > > Please, get in touch with plasmashell devs, I'm sure they will be glad to > get > any help in addressing that sort of issues. > > On Tue, 2021-03-16 at 15:34 +0100, Alberto Salvia Novella wrote: > > The thing is that plasmashell isn't always started via its service, at > least > > this is the case on my system. I shall look into that. > > > > On Tue, 16 Mar 2021 at 07:41, Konstantin Kharlamov <[email protected]> > wrote: > > > On Tue, 2021-03-16 at 01:29 +0100, Alberto Salvia Novella wrote: > > > > I have created this tool for the Plasma desktop: > > > > https://gitlab.com/es20490446e/plasma-leakguard > > > > > > > > Shall I announce it somewhere? > > > > > > > > (When replying please include my email address on the "to" field, as > I > > > > have > > > > mail delivery disabled for this list) > > > > > > (note: I'm just a random passer-by contributor) > > > > > > I think you better discuss this with plasmashell developers. Clearly, > memory > > > leaks need to be fixed instead of working them around. Although if > they deem > > > such tool as you suggest necessary, to me it seems easier to implement > by > > > creating a plasmashell user-level service with `MemoryMax=` variable > set and > > > being restartable (or, in case they wouldn't want to depend on > systemd, I > > > imagine it should be available with bare cgroups too). > > > > > >
