Adding a picture frame plasmoid (the one described here: https://userbase.kde.org/Plasma/PictureFrame ; it does not seem to have a separate category, so I am reporting it under the 'general' component) to the desktop causes plasmashell's memory consumption to grow indefinitely. Pressing the 'next' or 'previous' arrows to change the displayed image makes the memory consumption increase faster. Steps to reproduce: 1. Add a media frame plasmoid to the desktop. 2. Add a few pictures to it. 3. Open Ksysguard and observe the amount of RAM used by plasmashell. 4. Wait for the image to change, or change the image by pressing the buttons. Observed result: memory consumption by plasmashell increases with each image change. Expected result: plasmashell should not consume unreasonable amounts of memory (in this case, I have observed its memory usage rising to up to 1.3 GB) More info: If we go to the 'detailed memory information' for plasmashell in Ksysguard, we see that the bulk of the memory is allocated to 'heap', and this is the component that grows on each image change.
Duplicate of bug 381000?
Let's assume it is. If you can still reproduce it after bug 381000 is fixed, please add a comment. *** This bug has been marked as a duplicate of bug 381000 ***
As of now, the bug is still there. Unfortunately. KDE Plasma 5.11.3 KDE Frameworks 5.39.0 Qt 5.9.1 Kernel 4.13.0-16 kubuntu 17.10 ppa landing
I finally managed to track the memory leak in plasmashell into this widget. still there in both Fedora 26 and 27 beta. some details: KDE Plasma 5.10.5 KDE Framewoks 5.39.0 Qt 5.9.2 Kernel: 4.13.12-300 GLX: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) OpenGL version: 3.0 Mesa 17.2.4
Bug #386844 (the issue #381000 this is marked as a duplicate of was forked into two separate bugs for the memory issue and the CPU usage issue) has been marked as fixed in Qt version 5.9.2. However, I am still able to reproduce this issue with the following software versions: Plasmashell: 5.11.3 Qt5: 5.9.2 Frameworks: 5.40.0 Distro: Arch Linux
As of now, the bug is still there. Unfortunately. KDE Plasma 5.11.5 KDE Frameworks 5.41.0 Qt 5.9.1 Kernel 4.13.0-31 kubuntu 17.10 ppa landing 64 bit This bug seems closed, but problem was never solved. How to reopen?
Ruedi, see bug 368838.