Make Plasmashell more stable and predictable
Closed, InvalidPublic

Description

  1. The plasmashell is pretty unpredictable now. In the sense of RAM consuming from 100-120 Mb at start to 350-450 Mb a few days later. It's not good for home and work computers. Is it possible to limit caching or something like that? Settings for memory usage policy, maybe (as in Okular settings)?
  1. The plasmashell is crashing due incorrect widgets, it happens. I think, it would be great to select some comprehensively tested basic widgets like a panel, system tray, main menu, pager, etc for execution into the first, main plasmashell process, and all other widgets put in the second plasmashell process. Thereby the desktop will be work even if an incorrect widget will crash second plasmashell process. Also, tested, stable widgets can be placed on first lines of search results in Plasma dialog window.
voidfragment updated the task description. (Show Details)

This doesn't follow the template, and seems like too "micro" of a task. These goals are generally intended to be more "macro" in scope IMO.

This doesn't follow the template, and seems like too "micro" of a task. These goals are generally intended to be more "macro" in scope IMO.

Maybe you are right. Then where should I move it?

This doesn't follow the template, and seems like too "micro" of a task. These goals are generally intended to be more "macro" in scope IMO.

Maybe you are right. Then where should I move it?

https://bugs.kde.org. :)

Preferably one bug per issue/feature request.

ngraham, so what do you think about dividing plasmashell into 2 processes? Is it good idea or not?

ngraham, so what do you think about dividing plasmashell into 2 processes? Is it good idea or not?

See https://www.youtube.com/watch?v=KoTDUv1Piog

lydia added a subscriber: lydia.Jun 15 2019, 7:19 AM

Would you like to build this out to something larger or shall we close it?

IMO this should be closed as it's basically a bug report, not really a long-term goal.

ervin added a subscriber: ervin.Jun 23 2019, 1:03 PM

IMO this should be closed as it's basically a bug report, not really a long-term goal.

Agreed

mart added a subscriber: mart.Jun 25 2019, 10:57 AM

IMO this should be closed as it's basically a bug report, not really a long-term goal.

+1 it is indeed a bug that sometumes happens, but it's just that, a bug report

ngraham closed this task as Resolved.Jun 25 2019, 10:57 AM
ngraham claimed this task.

Please file bugs on https://bugs.kde.org for specific issues. Thanks!

ngraham removed ngraham as the assignee of this task.Jun 25 2019, 10:58 AM
ngraham changed the task status from Resolved to Invalid.