https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #16 from kevin.david.h...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #15 from Nate Graham ---
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 are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466634
Nate Graham changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #14 from kevin.david.h...@gmail.com ---
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 wrote:
>
https://bugs.kde.org/show_bug.cgi?id=466634
Nate Graham changed:
What|Removed |Added
Resolution|WAITINGFORINFO |DUPLICATE
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #12 from Nate Graham ---
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 are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #11 from kevin.david.h...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #10 from kevin.david.h...@gmail.com ---
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 wrote:
> https://bugs.kde.org/show_bug.cgi?id=466634
>
> --- Comment #9
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #9 from Nate Graham ---
Thanks. And if you plug in the second screen, does the memory use immediately
skyrocket?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #8 from kevin.david.h...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #7 from kevin.david.h...@gmail.com ---
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
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #6 from Nate Graham ---
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
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #5 from kevin.david.h...@gmail.com ---
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 wrote:
>
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #4 from Nate Graham ---
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
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #3 from kevin.david.h...@gmail.com ---
Multiple displays (2). Attached is shot of current display setup in system
settings.
On Wed, Mar 1, 2023 at 1:48 PM Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=466634
>
> Nate Graham
https://bugs.kde.org/show_bug.cgi?id=466634
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=466634
--- Comment #1 from kevin.david.h...@gmail.com ---
Created attachment 156870
--> https://bugs.kde.org/attachment.cgi?id=156870=edit
plasmashell after sitting idle overnight, almost all memory saturated
--
You are receiving this mail because:
You are
17 matches
Mail list logo
