| Summary: | Possible memory leak | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | hancerli <bhancerli> |
| Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | kde, nate, thomwalker732 |
| Priority: | NOR | ||
| Version First Reported In: | 5.21.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
hancerli
2021-04-24 11:09:43 UTC
>Is there any way to trace what consumes that much memory?
There is a tool called Heaptrack
That or just turning off applets individually till you nail it down.
I'm afraid there's not much we can do without some narrowing it down
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! (In reply to David Edmundson from comment #1) > >Is there any way to trace what consumes that much memory? > > There is a tool called Heaptrack > > That or just turning off applets individually till you nail it down. > > I'm afraid there's not much we can do without some narrowing it down Hi there, Seems I skipped your response, somehow, sorry. I just run the plasmashell with heaptrack and waiting for the memory usage to rise up again, then I'll share the report. Should I switch the status back to REPORTED? Btw, thanks for the tip. Here's the heaptrack analysis file. https://drive.google.com/file/d/1Ejj5GPR3iok-fsHCfKS_ncyu5GWreNXg/view?usp=sharing Can't add ass attachment since it's 170mb. I'm fairly new to heaptrack and it'll take some time for me to start understanding the content. So I decided to upload it asap if you'd like to analyze it. Bump x6. I'd appreciate if this bug takes priority - it might be causing other accidental threads being created in relation to memory leaks and mistaking side effects in other places (such as I did with plasma widgets). It makes it impossible to keep a desktop linux distro running KDE for several days and it's making the desktop environment give a really poor impression and experience. Hi hancerli. I'm sorry nobody was able to analyze the heaptrack data after you posted it. Unfortunately it's been a while, and loads of things have changed in the past four years, including a new major Qt version. Can I ask if you're still able to reproduce this in a new clean user account in Plasma 6.4 or later? Thanks! Hi Nate, It's unlikely that this bug report contains any valuable information since it's outdated in many aspects. I think we can simply close it (I'm not sure how to do it though) |