https://bugs.kde.org/show_bug.cgi?id=460813

            Bug ID: 460813
           Summary: Unknown memory usage after screen lock
    Classification: Plasma
           Product: kscreenlocker
           Version: 5.26.1
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: plasma-b...@kde.org
          Reporter: ruzgardeniz...@hotmail.com
                CC: bhus...@gmail.com
  Target Milestone: ---

SUMMARY
When I unlock the screen by typing password and hitting enter after locking the
screen or suspending the computer, I observe significant increase in memory
usage. This behavior does not happen all the time. it can happen randomly after
several days of uptime. The interesting part is that I cannot see which
application uses the memory. Even after logging out the KDE session, memory
usage is just there. I could not debug this behavior and I hope to find some
help from KDE devs.

An example of memory usage history:
* Before the lock or suspend, it is 10GB.
* After the unlocking, 20GB.
* After logging out, 10GB.

I can be sure that it happens just after the unlock and displaying the desktop
since I can feel the desktop getting sluggish for a second. One additional
note, the lock screen turns off the screen to save power, after a couple
seconds, the screen turns on again - I could not find a way to turn off my
screen from KDE.

STEPS TO REPRODUCE
1. Lock the screen
2. Unlock the screen

OBSERVED RESULT
The system memory usage spikes.

EXPECTED RESULT
The system memory should remain same

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Gentoo, kde-plasma/plasma-meta-5.26.1::gentoo
(available in About System)
KDE Plasma Version: 5.26.1
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
uname: Linux 6.0.2-gentoo-bwqr-x86_64 #2 SMP PREEMPT Wed Oct 19 22:04:33 +03
2022 x86_64 AMD Ryzen 5 5600X 6-Core Processor AuthenticAMD GNU/Linux
gpu: amd rx 580
mesa: 22.2.1

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to