The OSX Virtual Memory Management System – A Personal Experience – Continuous Deployment

I’ve been writing about Chrome bloat over the past few months because of the havoc it plays on my own system: MacBook Pro Mid-2012 2.5 GHz CPU Sierra OSX. In late summer of this year, I increased my RAM to 16Gb. The screenshot below shows the state of my system late Sunday night. I ran the Activity Monitor (it actually runs constantly) and selected the Memory tab. The “red-lining” is attributable to 14.55 GB of memory usage, of which roughly half is Compressed Memory, the other portion is App Memory. The running tasks, ordered in descending order, are most noticeably the Python interpreter and the kernel itself. Thereafter, there are a number of Google Chrome – Google Chrome Helper tasks lapping up resources. I found the following info on Apple’s Developer pages and they shed some light on the underlying issues, including an overview of the Virtual Memory System, Tips For Allocating Memory, Tracking Memory Usage and Finding Memory Leaks. These memory leaks have become a mini-obsession of mine. They are kudzu-like in their usurpation of resources. They happened before I doubled my RAM storage and are obviously happening after the fact. My own very preliminary conclusion is that application developers would do well to familiarize themselves with these principles and integrate them into their design decisions. What do you think or suggest be done about this issue?

Memory Pressure - Leak??
Memory Pressure – Leak??

You May Also Like

About the Author: Stephanie

Your comments are welcome!

%d bloggers like this: