That&#x27;s not really how it works. Both executables and shared libraries are mapped into the virtual address space of the process, then only stuff that is actually used will be faulted (read) into physical memory. At page granularity, so yes, there is some bloat due to unused functionality, but it&#x27;s not as bad as requiring the entire thing to be loaded into memory.