Bug 415828 - Memory leak
Summary: Memory leak
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-wayland (show other bugs)
Version: 5.17.4
Platform: Arch Linux Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-03 04:53 UTC by Jester Flint
Modified: 2020-03-20 17:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-32146-0.html (1.72 KB, text/html)
2020-03-03 10:49 UTC, Jester Flint
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jester Flint 2020-01-03 04:53:39 UTC
SUMMARY


STEPS TO REPRODUCE
1. Use a lot of RAM, i used google-chrome-stable, chromium, google-chrome-beta, okular and music player (i used about 5/8 gb) for some time (atleast an hour or 2).  
2. Close all the applications

OBSERVED RESULT
Plasmashell using 15-20% CPU of my 8 core i7-6700hq. 
Plasmashell using 600 mb ram. 

EXPECTED RESULT
Plasma shell not using this much of cpu and RAM

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.4.6-arch3-1 (kernel)
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0

ADDITIONAL INFORMATION
Sorry if its a duplicate, i searched and found one with opensuse and different plasma version. 
Thank you for the awesome Plasma DE.
Comment 1 David Edmundson 2020-02-09 15:43:20 UTC
You've tagged this as generic-wayland, I assume this supposed memory leak doesn't happen on X?

Can you narrow this down any more by removing widgets and see if you can identify what triggers this?

There's not a lot we can do with the report otherwise.
Comment 2 Bug Janitor Service 2020-02-24 04:33:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Jester Flint 2020-03-03 10:49:27 UTC
Created attachment 126560 [details]
attachment-32146-0.html

I happened to reinstall the whole system and right now using X. didnt
notice any problems right now.

On Sun, Feb 9, 2020 at 9:13 PM David Edmundson <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=415828
>
> David Edmundson <kde@davidedmundson.co.uk> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>                  CC|                            |kde@davidedmundson.co.uk
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from David Edmundson <kde@davidedmundson.co.uk> ---
> You've tagged this as generic-wayland, I assume this supposed memory leak
> doesn't happen on X?
>
> Can you narrow this down any more by removing widgets and see if you can
> identify what triggers this?
>
> There's not a lot we can do with the report otherwise.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Bug Janitor Service 2020-03-18 04:33:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Christoph Feck 2020-03-20 17:45:43 UTC
Thanks for the update; changing status.