| Summary: | When the desktop is running, even at idle, plasmashell will consume all of my 32GB of memory resulting in a system freeze. | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | kevin.david.hall |
| Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | nate |
| Priority: | NOR | Keywords: | regression |
| Version: | 5.27.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
plasmsashell memory usage after 1 hour 40 minutes of uptime
plasmashell after sitting idle overnight, almost all memory saturated display setup.jpeg kscreen_console_bug_output.txt attachment-3365820-0.html attachment-3374239-0.html attachment-3375705-0.html attachment-3387160-0.html attachment-3493340-0.html attachment-3857887-0.html |
||
|
Description
kevin.david.hall
2023-03-01 05:32:29 UTC
Created attachment 156870 [details]
plasmashell after sitting idle overnight, almost all memory saturated
Do you have multiple screens, or only one? Created attachment 156899 [details] display setup.jpeg Multiple displays (2). Attached is shot of current display setup in system settings. On Wed, Mar 1, 2023 at 1:48 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=466634 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC| |nate@kde.org > > --- Comment #2 from Nate Graham <nate@kde.org> --- > Do you have multiple screens, or only one? > > -- > You are receiving this mail because: > You reported the bug. Hmm, reminds me of Bug 466362. Does it stop happening if you only have one screen plugged in? If so, does it start happening again when you plug in the second screen? Also can you run `kscreen-console bug` and paste the "EDID" sections for your screens? Thanks! Created attachment 156900 [details] kscreen_console_bug_output.txt Put it in a txt file since it's so long. I haven't tried it with only one screen. Does it need to be unplugged, or will powered down suffice? On Wed, Mar 1, 2023 at 2:36 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=466634 > > --- Comment #4 from Nate Graham <nate@kde.org> --- > Hmm, reminds me of Bug 466362. Does it stop happening if you only have one > screen plugged in? If so, does it start happening again when you plug in > the > second screen? > > Also can you run `kscreen-console bug` and paste the "EDID" sections for > your > screens? > > Thanks! > > -- > You are receiving this mail because: > You reported the bug. Unplugged would be better, since it's DisplayPort. Looks like your two screens report identical serial numbers. Despite thir, their EDID hash values do differ, so that's nice at least. Definitely curious to know if the issue goes away with only one screen plugged in. Created attachment 156901 [details] attachment-3365820-0.html Okay, I'll pull one monitor. plasmashell is currently sitting at 20.3Gb memory usage as of this email. I'll report back in a couple of hours as to the change or lack thereof. On Wed, Mar 1, 2023 at 2:43 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=466634 > > --- Comment #6 from Nate Graham <nate@kde.org> --- > Unplugged would be better, since it's DisplayPort. > > Looks like your two screens report identical serial numbers. Despite thir, > their EDID hash values do differ, so that's nice at least. > > Definitely curious to know if the issue goes away with only one screen > plugged > in. > > -- > You are receiving this mail because: > You reported the bug. Created attachment 156902 [details] attachment-3374239-0.html plasmashell got to about 23Gb in size and crashed/restarted. When it respawned, it grabbed ~390Mb of memory instead of the 2Gb that I was seeing earlier on startup. Still have the one monitor removed from desktop, running in single monitor since the last email. On Wed, Mar 1, 2023 at 2:45 PM Kevin Hall <kevin.david.hall@gmail.com> wrote: > Okay, I'll pull one monitor. plasmashell is currently sitting at 20.3Gb > memory usage as of this email. I'll report back in a couple of hours as to > the change or lack thereof. > > On Wed, Mar 1, 2023 at 2:43 PM Nate Graham <bugzilla_noreply@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=466634 >> >> --- Comment #6 from Nate Graham <nate@kde.org> --- >> Unplugged would be better, since it's DisplayPort. >> >> Looks like your two screens report identical serial numbers. Despite thir, >> their EDID hash values do differ, so that's nice at least. >> >> Definitely curious to know if the issue goes away with only one screen >> plugged >> in. >> >> -- >> You are receiving this mail because: >> You reported the bug. > > Thanks. And if you plug in the second screen, does the memory use immediately skyrocket? Created attachment 156903 [details] attachment-3375705-0.html It rose to ~400Mb. I'll keep an eye on it and let you know if it climbs over time. On Wed, Mar 1, 2023 at 4:24 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=466634 > > --- Comment #9 from Nate Graham <nate@kde.org> --- > Thanks. And if you plug in the second screen, does the memory use > immediately > skyrocket? > > -- > You are receiving this mail because: > You reported the bug. Created attachment 156906 [details] attachment-3387160-0.html It's been almost 3 hours. Still hovering in the 400Mb of memory range. So, is there a permanent fix, or do I need to start my machine with 1 monitor for the foreseeable future? On Wed, Mar 1, 2023 at 4:34 PM Kevin Hall <kevin.david.hall@gmail.com> wrote: > It rose to ~400Mb. I'll keep an eye on it and let you know if it climbs > over time. > > On Wed, Mar 1, 2023 at 4:24 PM Nate Graham <bugzilla_noreply@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=466634 >> >> --- Comment #9 from Nate Graham <nate@kde.org> --- >> Thanks. And if you plug in the second screen, does the memory use >> immediately >> skyrocket? >> >> -- >> You are receiving this mail because: >> You reported the bug. > > Definitely not a fix, just a workaround that helps to confirm that this is Bug 466362. We'll see if we can get it fixed soon! *** This bug has been marked as a duplicate of bug 466362 *** Created attachment 156942 [details] attachment-3493340-0.html Awesome Nate, thanks for the quick turnaround and attentiveness. I really appreciate it. Wish the devs I work with were this quick. On Wed, Mar 1, 2023 at 9:39 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=466634 > > --- Comment #12 from Nate Graham <nate@kde.org> --- > Definitely not a fix, just a workaround that helps to confirm that this is > Bug > 466362. We'll see if we can get it fixed soon! > > -- > You are receiving this mail because: > You reported the bug. Well the issue isn't fixed (just marked as a duplicate of another known issue) so don't thank me yet! :) Created attachment 157049 [details] attachment-3857887-0.html I get it. Also, the stability did NOT survive a reboot (and I didn't expect it to) but I did recreate the method of removing a monitor and rebooting as instructed, but still getting over usage of memory even with a single monitor. On Mon, Mar 6, 2023 at 9:47 AM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=466634 > > --- Comment #15 from Nate Graham <nate@kde.org> --- > Well the issue isn't fixed (just marked as a duplicate of another known > issue) > so don't thank me yet! :) > > -- > You are receiving this mail because: > You reported the bug. |