Purge Command Broken 10.8.1

Discussion in 'OS X Mountain Lion (10.8)' started by isrefel, Aug 23, 2012.

  1. isrefel macrumors member

    Jul 8, 2012
    Just updated to 10.8.1 on my 2012 MBA. Someone had commented on OSXDaily that their purge command in terminal was now returning this error.

    [ERROR] <CPPathUtils.c:526> The device-file for this operating system, 'osx-12.1.0.xml', was not found. An attempt to revert to a previous revision of the OS device-file: 'osx-12.0.0.xml' has been made. Please file a Radar report with Apple, on the 'CoreProfile' component, version 'X'.

    I tested the command on my machine and it also returns this error. OS X 12.1.0? Anyone else having this issue?
  2. GGJstudios macrumors Westmere


    May 16, 2008
    You don't need to use purge. It removes the advantage that inactive memory has, without adding any benefit, since inactive memory is the same as free memory in all other respects.

    Mac OS X: Reading system memory usage in Activity Monitor
  3. Mal macrumors 603


    Jan 6, 2002
    To be fair, if the OP is a developer, there are legitimate use cases for the purge command. It shouldn't be inoperable, unless it's been replaced with another function.

  4. GGJstudios macrumors Westmere


    May 16, 2008
    I agree a developer might have use for it. The problem is many non-developer users mistakenly think they need it.
  5. isrefel thread starter macrumors member

    Jul 8, 2012
    Questions still stand. Can anyone replicate this?
  6. tarjan macrumors regular

    Aug 11, 2006
    I run a number of high memory use applications and can get up near 8gb pretty quickly. Even if my primary application is getting larger and needs more ram, my inactive memory might stay at 2+gb in size in Snow leopard and Lion.

    At that point he hard drive chugs and my system becomes incredibly inefficient swapping huge amounts of ram for the active application without releasing anything from older or non active apps/cache..

    Run purge and bam, the main application is working properly again and I see no degredation otherwise.

    I'm sure this is a specific and special case and it might be many months between times where this does occur, definitely not daily, but a normal user MAY need it. They just need to know, 100%, that they do. Hopefully this is all actually resolved in ML so it would be a moot point, but I just in case..
  7. Feed Me macrumors 6502a

    Feed Me

    Jan 7, 2012
    Location Location
  8. Icy1007 macrumors 65816


    Feb 26, 2011
    Cleveland, OH
    OS X 12.1.0 refers to Darwin v12.1.0.

    I've heard that purge still works even though it gives that error message.
  9. rodknocker macrumors 6502

    Jul 4, 2011
    It sill works :)
  10. dyn macrumors 68030

    Aug 8, 2009
    Purge only forces the disk cache to be purged. There are other items in inactive memory as well.
  11. Icy1007 macrumors 65816


    Feb 26, 2011
    Cleveland, OH
    Actually it doesn't. Purge releases all inactive memeory, it has nothing to do with the disk.
  12. davidlv macrumors 65816

    Apr 5, 2009
    Kyoto, Japan
    Yes, same error message appears here too, but as mentioned above, the purge actually still works. Apple must (?) know the reason that error occurs, but why wasn't it resolved? Seems that an error message like that may be valid in a developer's release, but in this public release, it just seems sloppy.:eek:
    Definitely not :cool:
  13. dyn macrumors 68030

    Aug 8, 2009
    That's not what Apple nor the documentation say:

    From the purge manual (man purge).

    From the Apple kb-article: https://support.apple.com/kb/HT1342

    Again: purge does not release all inactive mem, it only writes the disk cache (which resides in memory) to disk. This is done automatically every x time anyway. Purging is quite pointless.
  14. Macman45 macrumors G5


    Jul 29, 2011
    Somewhere Back In The Long Ago
    See my post from last night, it's a known issue..For a while, terminal wouldn't work at all for me on all 3 Macs...got it back, but as you say, purge and a few other commands (also people having issues with old scripts) remain broken.


    I suspect Apple will probably patch this fairly quickly though
  15. iOrbit macrumors 6502a

    Mar 8, 2012
    i just ran the purge command, no error.

    updated to 10.8.1. last night
  16. netnothing macrumors 68040


    Mar 13, 2007
    Same here.....command throws that error, but memory is still purged.

  17. ikol-22 macrumors newbie

    Jul 8, 2010
    Torino - Italy
    I've got the same here (Italy) with a Purge command just after the last update 10.8.1 and I confirm that when Inactive memory is over than Free the system is definitely slow.
  18. wd40 macrumors newbie

    Nov 5, 2007
    I can replicate this error as well.

    Now, this may not be the right thread for this, but I'm losing a ridiculous amount of time each day on memory time-out and restarts.

    I have a 2011 2.2GHz i7 with 8GB of RAM and it behaves as though there were only 2GB. If chrome is open, inactive memory jumps above 3GB and free falls below 150MB.

    Running 'purge' doesn't clear the 3GB of inactive -

    What the heck is the 3GB inactive storing and where is it storing it?? No matter what I do to clear up chrome (delete local storage, extensions, etc.), it always returns when I start the app up.

    I'm so tired of the color wheel and bi-hourly restarts...

    Any suggestions? I've google the heck out of this issue and there's a lot of discussion on it. But no one seems to have an answer that addresses the cause. Apps like "Free Memory" don't speed things up for me at all. If anything, they make things worse (if that's even possible)
  19. EHLO macrumors newbie

    Feb 3, 2010
    It's useful from a user perspective.
    On a MacBook Air with 4MB memory it will swap to disk when low, see pageouts with the top command.
    Using purge stops the pageouts and reduces writes to the SSD.
  20. Watabou macrumors 68040


    Feb 10, 2008
    United States
    I don't know. For some reason ML just doesn't want to free up inactive memory. I will have less than 20MB of free memory remaining with over a GB of inactive memory just sitting around and when I get beach balls, OS X doesn't seem to purge that inactive memory when the app needs more. It's only when I manually purge that everything is fine again and the app is responsive again.
  21. dukebound85 macrumors P6


    Jul 17, 2005
    5045 feet above sea level
    Purging has boosted my system performance when one app is using alot of ram (as in all of my ram)
  22. TheMTtakeover macrumors 6502


    Aug 3, 2011
    Hmm. So people can get windows computers cheaper and they seem to be the ones that "just work". No need to purge memory. It as an OS can handle ram like an OS is supposed to.
  23. rthr macrumors newbie

    Aug 27, 2012
    Fresh OS X 10.8 install (updated to 10.8.1) and a fresh copy of Apple's Logic (updated to 9.1.7).

    A plugin in Logic tells me that I'm out of memory. I have 43MB Free and about 10GB Inactive. After a purge, suddenly I'm not out of memory and can load more samples.

    Or a musician using Apple's flagship DAW.

    How else do I use the memory in my computer, because it's not automagically using my Inactive memory as though it is Free? :mad:
  24. flyc14 macrumors newbie

    Jul 9, 2010
    sloppy release from Apple

    purge throws the following error
    flycs-MacBook-Air:~ flyc$ purge
    [ERROR] <CPPathUtils.c:526> The device-file for this operating system, 'osx-12.1.0.xml', was not found. An attempt to revert to a previous revision of the OS device-file: 'osx-12.0.0.xml' has been made. Please file a Radar report with Apple, on the 'CoreProfile' component, version 'X'.

    This is the most annoyance I've got for investing in an OSX upgrade. Since the upgrade, OSX has crashed a few times and battery life has reduced. Hangs for about 7 seconds, when woken from sleep. Shutdown, which used to take 3 seconds now wavers between 15 seconds and 10.

    My previous 2 upgrades (Leopard to snow leopard & snow leopard to Lion) made my system faster and more stable. 10.8 had fewer issues, 10.8.1 appears to have more issues than 10.8. I've not installed a single piece of new software between Lion, Mountain Lion and Mountain Lion 10.8.1. The only change in the system is OS X upgrade; I wish I could rollback the upgrade.

    Steve - I dearly miss you.
  25. fartey macrumors newbie

    Mar 17, 2010
    New Zealand
    Same I've got a late 2010 mac mini and it says the same thing. I recently installed memcheck from an article at mac|life.com. After that I have the same identical error message when ever I use purge. How do you even report it to apple. I was doing the memcheck because my mac mini was so slow I thought my 4GB memory was defected anyway I got the same message.

Share This Page