| Summary: | High RAM memory consumption | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | joaoeudes7 |
| Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | critical | CC: | mikaela.szekely, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.23.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Use of memory on system | ||
|
Description
joaoeudes7
2021-11-11 16:03:17 UTC
Created attachment 143458 [details]
Use of memory on system
Memory issues like this are very difficult to debug without at least a bit of information what activities cause the memory to go so high. Can you do a little bit of digging to try to figure that out? For example: - Does it increase with every notification you receive - Do you use a slideshow or animated wallpaper, and it goes up with every new image etc. (In reply to Nate Graham from comment #2) > Memory issues like this are very difficult to debug without at least a bit > of information what activities cause the memory to go so high. Can you do a > little bit of digging to try to figure that out? For example: > - Does it increase with every notification you receive > - Do you use a slideshow or animated wallpaper, and it goes up with every > new image > > etc. The Telegram and Slack was opened, after unlock the lock screen the usage of RAM was highly and show same notification. No, don't have animations, only conky What notification? Can you reboot the system and monitor RAM usage and see if you can figure out what specific event or app makes it go up like that? 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |