STEPS TO REPRODUCE Unclear. I noticed this issue after the following: 1. Accidentally opening a 70gb PDF using KWrite (it was a .txt file for some reason). I had to kill the program with system monitor. 2. running multiple virtual machines under KVM/QEMU OBSERVED RESULT Over 10GB of system memory is being used.... but System Monitor has no idea what it is, and neither do I EXPECTED RESULT Memory is not in use when programs are closed and/or System Monitor sees what program(s) are using up all the memory. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.2 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION Memory: 15.6 GiB of RAM Image of running processes using `top`: https://imgur.com/a/iBofbfG I'm honestly just kind of baffled and I've had this issue multiple times recently and had to reboot to fix it. I'm not sure what the cause could be because I (barely) remember doing various different tasks. It could be KWrite, that is a common denominator but wouldn't make much sense.....
It sounds like you might be running into some kind of kernel memory leak. You'll want to start with looking at `/proc/meminfo`, which is the file we use for reading global memory info. "Free" memory is the "MemAvailable" field in this file, while "Used" is calculated as "MemTotal - MemAvailable". There are a bunch more fields in that file that may be relevant for your specific issue. For example, "Slab", "SReclaimable" and "SUnreclaim" indicate total memory allocated by the kernel's Slab allocator and how much of that can be reclaimed and how much can't be reclaimed. The Slab allocated memory is memory that is not available to applications, so it is not listed in the process view.
.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
(In reply to Arjen Hiemstra from comment #1) > It sounds like you might be running into some kind of kernel memory leak. > You'll want to start with looking at `/proc/meminfo`, which is the file we > use for reading global memory info. "Free" memory is the "MemAvailable" > field in this file, while "Used" is calculated as "MemTotal - MemAvailable". > > There are a bunch more fields in that file that may be relevant for your > specific issue. For example, "Slab", "SReclaimable" and "SUnreclaim" > indicate total memory allocated by the kernel's Slab allocator and how much > of that can be reclaimed and how much can't be reclaimed. The Slab allocated > memory is memory that is not available to applications, so it is not listed > in the process view. Noted. Update: It happens when I wake the computer from sleep. I logged in to see that I had 8/16gb used up and immediately went "Oh no" and restarted the computer before it could crash. I saw the updates in this thread when I checked my email. Maybe there's some script I could slap together to log some data when I notice it happening? It's pretty fast. I could just output that command to a file to see where the memory was allocated. I'm not sure how helpful that will be necessarily (?)
Note: I watched the memory usage slowly tick up as I sat on the desktop, before I decided to restart.
#!/bin/bash date >> gonnacrash.txt cat /proc/meminfo >> gonnacrash.txt echo " " >> gonnacrash.txt 🤷🏻♂️
Created attachment 176775 [details] Memory usage while apparent leak was occuring (after waking from sleep) Memory rapidly filling up for unknown reasons after waking from sleep. It didn't crash this time, after it got up to like 8gb used it reset down to 2gb and stopped filling up.
*** Bug 496653 has been marked as a duplicate of this bug. ***
There is nothing for us to do here, so I'm closing this.
(In reply to Arjen Hiemstra from comment #9) > There is nothing for us to do here, so I'm closing this. Ok, go for it. I'm not sure what even caused this issue, but I haven't had a problem with it for some time now, It was probably passively fixed in an update, I imagine.