https://bugs.kde.org/show_bug.cgi?id=474609
Bug ID: 474609
Summary: /usr/bin/plasmashell --no-respawn causes severe
lagginess by reclaiming enormous amounts of virtual
ram
Classification: Plasma
Product: plasmashell
Version: 5.27.8
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: generic-performance
Assignee: plasma-b...@kde.org
Reporter: jmbar...@googlemail.com
Target Milestone: 1.0
SUMMARY
Since I updated to Plasma 5.27.8, the /usr/bin/palsmashell --no-respawn claims
a huge amount of RAM (up to 2/3rd of system RAM
Background: I have a 32 GB Ram amd G5700 System. I'm working (at this time)
mostly with Obsidian.md, which, as an Electron-App itself uses lots of
ressources (unfortunately). But since installing KDE Plasma 5.27.8 I experience
an immense lagginess. I first thought, that this was a problem with
Obsidian.md, but than I noticed, that the RAM usage stays the same even without
Obsidian running. This persists and gets even worse after standby (it acutally
stands - without little temporal changes - at 20.2 GB.
Only way to fix it (temporarily): restart system.
htop reports
10.7G VIRT, 833M RES, 290MSHR for plasmashell -- no-respawn (about 30
processes)
5329MB VIRT, 71936M RES, 55040 SHR for QtWebEngineProcess (about 10 processes)
KDE Systemmonitor reads about 630 MiB RAM usage for plasmashell ...
I don't understand what's going on here, I'm not a IT-Systemsengineer, but this
does not seem right!
STEPS TO REPRODUCE
1. work with some heavy load productive systems
2. Go to standby mode
3. reactivate system ...
OBSERVED RESULT
severe lagginess of productive programs
EXPECTED RESULT
Swift working of the system, as it was until 5.27.7 ...
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux: 6.5.3-1-default
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
ADDITIONAL INFORMATION
By the way: why is it necessary, that the calendar reminder of Akonadi
constantly uses more than 930 MiB of Ram in idle ???
--
You are receiving this mail because:
You are watching all bug changes.
