Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

System has started using all my app memory and having to restart every few minutes. Chrome and firefox only apps that seem to cause the problem. Anyone have any suggestions? 16gb memory early 2009 mac pro

My mac pro (early 2009 16GB memory) has started using up all my app memory and having to restart every few minutes. This only since installing ElCapitan.


Happens when have both Firefox and Chrome open.


Any idea what is wrong or what I can do about it.

Mac Pro, Mac OS X (10.5.2)

Posted on Nov 20, 2015 3:07 PM

Reply
Question marked as Best reply

Posted on Nov 21, 2015 6:02 PM

There is 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. It can happen for two reasons:

A long-running process with a memory leak (a kind of bug)

Not enough memory for your usage pattern

Please note that if the cause is a memory leak, installing more memory will not help. That's likely if you already have more than 4 GB of memory. Tracking down a memory leak can be difficult, and it may come down to a process of elimination.

These instructions are for OS X 10.9 and later. Some details may be slightly different for earlier versions of OS X.

When you notice the slowdown, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select

View ▹ Columns ▹ Real Memory

from the menu bar.

If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.

"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.

If you don't have an obvious memory leak, the options are to install more memory (if possible) or to run fewer programs simultaneously.

The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:

sudo leaks -nocontext -nostacks process | grep total

where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

1 reply
Question marked as Best reply

Nov 21, 2015 6:02 PM in response to rwjordan

There is 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. It can happen for two reasons:

A long-running process with a memory leak (a kind of bug)

Not enough memory for your usage pattern

Please note that if the cause is a memory leak, installing more memory will not help. That's likely if you already have more than 4 GB of memory. Tracking down a memory leak can be difficult, and it may come down to a process of elimination.

These instructions are for OS X 10.9 and later. Some details may be slightly different for earlier versions of OS X.

When you notice the slowdown, open the Activity Monitor application and select All Processes from the View menu, if it's not already selected. Select the Memory tab. Click the heading of the Real Mem column in the process table twice to sort the table with the highest value at the top. If you don't see that column, select

View ▹ Columns ▹ Real Memory

from the menu bar.

If one process (excluding "kernel_task") is using much more memory than all the others, that could be an indication of a leak. A better indication would be a process that continually grabs more and more real memory over time without ever releasing it. Here is an example of how it's done.

"Wired" memory should be a small part of the total. That memory is not swapped, but it makes less physical memory available which may then result in swapping. If you have a lot of wired memory, that's usually an indication of a memory leak in a third-party program that modifies the operating system at a low level. Ask for guidance in that case.

If you don't have an obvious memory leak, the options are to install more memory (if possible) or to run fewer programs simultaneously.

The next suggestion is only for users familiar with the shell. For a more precise, but potentially misleading, test, run the following command:

sudo leaks -nocontext -nostacks process | grep total

where process is the name of a process you suspect of leaking memory. Almost every process will leak some memory; the question is how much, and especially how much the leak increases with time. I can’t be more specific. See the leaks(1) man page and the Apple developer documentation for details.

System has started using all my app memory and having to restart every few minutes. Chrome and firefox only apps that seem to cause the problem. Anyone have any suggestions? 16gb memory early 2009 mac pro

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.