The next suggestion is only for users familiar with the shell. If you don't have an obvious memory leak, the options are to install more memory (if possible) or to run fewer programs simultaneously. If most of the memory is wired, that may be an indication of a memory leak in a third-party program that modifies the operating system at a low level. That memory is not swapped, but it makes less physical memory available which may then result in swapping. "Wired" memory should be less than half of the total. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. When you notice the slowdown, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Some details may be slightly different for earlier versions of OS X. These instructions are for OS X 10.9 and later. Tracking down a memory leak can be difficult, and it may come down to a process of elimination. That's likely if you already have more than 4 GB of memory. Please note that if the cause is a memory leak, installing more memory will not help. It can happen for two reasons:Ī long-running process with a memory leak (a kind of bug) There may be excessive swapping of data between physical memory (that is, the memory chips on the logic board) and virtual memory (one or more files on the startup volume.) That activity is relatively slow and causes the whole system to be less responsive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |