Created attachment 158172 [details] output of: 'while /bin/true ; do date >> tmp/plasmashell_mem.log; ps -e -o comm,%cpu,cputime,etime,rss,%mem | grep -E "plasmashell|COMMAND" | tee -a tmp/plasmashell_mem.log; sleep 30m; done' SUMMARY Plamashell starts using about 400kbytes of memory and after 5:30h it is using more than 8G ! Must be a memory leak somewhere. STEPS TO REPRODUCE I collected the memory used by plasmasheel with a simple script. The data is attached. Note that, between 12:00h and 13:30h it was my lunch time, the computer was idle, even so, the memory usage increased from 3665792 to 5375696 bytes. After 5:30h since the KDE was started it was using 8142588 bytes. OBSERVED RESULT Memory usage increase over time. EXPECTED RESULT A more discrete usage of memory. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230413 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: ASUS ADDITIONAL INFORMATION Please , see the attached file. It has the used plasmashell memory in 30m intervals.
Do you have multiple screens?
Created attachment 158209 [details] attachment-3867394-0.html Yes. I have 2 monitors, 4 workspaces, 2 activities. Em ter., 18 de abr. de 2023 22:26, Nate Graham <bugzilla_noreply@kde.org> escreveu: > https://bugs.kde.org/show_bug.cgi?id=468628 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > Component|general |generic-performance > CC| |nate@kde.org > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Do you have multiple screens? > > -- > You are receiving this mail because: > You reported the bug.
Aha, in that case it is most likely Bug 466362 which is fixed for the upcoming Plasma 5.27.5 release. *** This bug has been marked as a duplicate of bug 466362 ***