13 Replies Latest reply: Jun 28, 2013 10:44 AM by macjack
acorngraphix Level 1 (0 points)

I have a MacBook Pro 2.5GHz  i7, SSD (256GB) that i use for my OS and Applications.  I am running Mountain Lion [10.8.4] and recently my storage space and fans have been acting "weird".  The RAM is also maxed out at 16GB.   A lot of times my fans come on max speed and there are no processes or reason for them flairing up.  I read somewhere that to eliminate these odd fan problems to remove the battery and hold the power  button for 5-10 seconds.  My model MacBook Pro has T screw holding the battery in and has big warnings stating not to remove the battery. 


Back to the main problem, i watched my Disk Info move from around 100 GB of free space down to 30 GB with no rhyme or reason.  It was just idle.

I have searched and read and ran Disk Utility and Onyx and made sure there are no crazy logs or hidden files.  I turned off time machine as well, thinking the random snapshots were hogging space.



any help will be much appreciated



MacBook Pro, OS X Mountain Lion (10.8.4)
  • macjack Level 9 (51,622 points)

    OmniDisksweeper can help you find what's hogging your disk space.

  • Linc Davis Level 10 (192,265 points)

    There is excessive swapping of data between physical memory and virtual memory.


    That can happen for two reasons:


    • You have a long-running process with a memory leak (i.e., a bug), or
    • You don't have enough memory installed for your usage pattern.


    Tracking down a memory leak can be difficult, and it may come down to a process of elimination.


    In the Activity Monitor application, select All Processes from the menu in the toolbar, if not already selected. 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.


    The process named "Safari Web Content" renders web pages for Safari and other applications. It uses a lot of memory and may leak if certain Safari extensions or third-party web plugins are installed. Consider it a prime suspect.


    If you don't have an obvious memory leak, your 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.

  • acorngraphix Level 1 (0 points)

    I have done both things suggested to no prevail.  When running Activity Monitor, kernel_task is 1.03 GB, Safari is 297.1 MB, mds is 243 MB and then it drops off drastically.... so no mystery action sucking my storage dry.

  • Linc Davis Level 10 (192,265 points)

    Select the System Memory tab. What values are shown in the bottom part of the window for Page outs and Swap used?

  • acorngraphix Level 1 (0 points)

    Page outs = 4.2

    Swap used = 0 bytes

  • Linc Davis Level 10 (192,265 points)

    4.2 what?

  • acorngraphix Level 1 (0 points)

    oops sorry.... 4.2 MB

  • Linc Davis Level 10 (192,265 points)

    ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.


    Back up all data now.


    Install ODS in the Applications folder as usual. Quit it if it's running.


    Triple-click the line of text below to select it, then copy the selected text to the Clipboard (command-C):

    sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper

    Launch the Terminal application in any of the following ways:


    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)


    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.


    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.


    Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.


    The application window will open, eventually showing all files in all folders. It may take some minutes for ODS to list all the files.


    I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means. When in doubt, leave it alone or ask for guidance.


    When you're done with ODS, quit it and also quit Terminal.

  • acorngraphix Level 1 (0 points)

    i will read through your Terminal instructions in a few moments.  i just wanted to say that while flipping to my dashboard for a second i noticed something strange on my iStat widget.  It seems as though "MobileBackups" is occupying 237.7 GB of space.  What is this [excuse me, long night and too lazy to search]  and can it be disabled if this is the root to the problem.




  • acorngraphix Level 1 (0 points)

    I may have inadvertently stumbled upon my problem.  A rather large file stalled out while printing yesterday and might have been sucking me dry.... i will post back after monitoring my free space for a little while.


    thanks for your continued responses though.



  • acorngraphix Level 1 (0 points)

    Okay that appeared to be the problem.... a stalled out print queue that crashed while sending information.

    Thanks for all the help and different options.




  • macjack Level 9 (51,622 points)

    Glad to hear you found the problem!