I'm using Bodhi Linux, and I've noticed some odd behavior with RAM usage after closing programs. For instance, when I open Chromium to browse and then close it, my RAM usage stays around 1GB higher than it was before I opened it. This issue seems to happen with other applications too, like when I run and close Zoom or install some packages in the terminal. Even when I'm not actively using anything, my RAM usage creeps up to about 75%.
I'm looking for advice on how to close a program and ensure that all associated processes are completely terminated. I've tried using htop to monitor processes, but I can't see any leftover entries for the programs I close. I hesitate to randomly kill processes since that could cause issues. Any tips on how to handle this?
3 Answers
Make sure to check your settings! Sometimes there are options related to memory management or caching that might affect how RAM is allocated and freed up after closing programs.
If your apps aren't shutting down correctly, there could be some background services running that you're unaware of—try running `ps aux` in the terminal to list all active processes as well. That might give you a clearer view of what's left running after you close applications.
You might be experiencing a memory leak from one of the programs or a change in how the system manages RAM with your current installation. It’s wise to look out for residual processes, but sometimes apps just don’t release RAM properly.
Try monitoring memory usage over time and see if it stabilizes after a few reboots. Also, if your previous Bodhi install managed RAM better, it could help to check if you can revert to that version or adjust some settings in your current install that might be causing the issue.
Monitoring tools like pmemstat could also help you track this down further.
Managing memory on Linux can be tricky! One thing to keep in mind is that Linux handles free and used memory differently than you might expect. Even after closing an app, memory usage might not drop as you anticipate due to cached memory that the system can quickly repurpose.
Instead of just focusing on the 'Used' memory, check your 'Available' memory in tools like htop. This gives you a better picture of what's genuinely free. If you're still concerned about residual processes, using a tool like pmemstat can help you see exactly what's consuming your RAM and kill any pesky processes hanging around.
Thanks for the info! I think I've just misunderstood how Linux tracks memory usage. I’ll definitely start checking the available memory to see if it helps ease my concerns.