Bug 29360 - Plasmashell memory leak when using slideshow
Summary: Plasmashell memory leak when using slideshow
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-11 22:25 CEST by Emmanuel ROBERT
Modified: 2021-08-17 10:40 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Emmanuel ROBERT 2021-08-11 22:25:24 CEST
Description of problem:
- Memory leak of the plasmashell process when using a slideshow 
- Plasmashell's memory occupation increases continuously
- Selecting a static background image as a replacement for the slideshow fixes the problem

Version-Release number of selected component :
- KDE Plasma 5.20.4
- One desktop, 4 activities including a slideshow
- KDE Frameworks 5.76.0
- Qt 5.15.2
- Kernel 5.10.56-desktop-.mga8
- OS 64-bit
- 16 Go RAM

How reproducible:
All the time

Steps to Reproduce:
1. create a folder containing two big pictures (2Mo each for instance)
2. create 4 activities with a slideshow (time 15s) pointing to the picture folder
3. visit all activities one time to start the leak
3. survey the memory consumption with the plasmoid
Comment 1 Emmanuel ROBERT 2021-08-11 23:52:28 CEST
I reboot the computer after step 2
Comment 2 Marja Van Waes 2021-08-12 16:58:51 CEST
Assigning to our KDE maintainers

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 3 Emmanuel ROBERT 2021-08-17 10:40:52 CEST
I have launched kcmshell5 qtquicksettings 
set Render loop to "Basic"
and Rendering backend to "Software".
I noticed a degradation of the Plasma rendering : I can no longer see the text below my desktop icons, only the picture, but it stopped the leak. 
I can no longer reproduce the leak problem. Everything looks stable.

What is the explanation ?
Which software is the culprit ?
When will it be fixed in Mageia8 ?

Note You need to log in before you can comment on or make changes to this bug.