Re: a way to clear inactive RAM
Hi, Thanks for the replies. I was trying to achieve what essentially free memory apps on the Mac AppStore do. The RAM usage can be divided into four parts as shown in Activity Monitor. 1. Free 2. In-active 3. Active 4. Wired When I used my earlier app to allocate memory equal to free + inactive bytes, for the execution of the program it used to make the system less responsive for a few seconds and on release and quitting the app, most of the inactive memory would shift under free. e.g. if free is 1GB and inactive is 1.5GB, then after run, free would be 2.45GB and inactive just 50MB. Thanks again, Nick On 06-Nov-2012, at 2:29 AM, Alex Zavatone z...@mac.com wrote: Not sure what RAM clearing means but if you want to purge the disk cache, check out man purge in the terminal. On Nov 5, 2012, at 1:54 PM, Nick Rogers wrote: Hi, I am assigned this small utility which should clear inactive RAM. I know Mac OS X manages memory quite efficiently and inactive RAM also has a purpose. But I have to make this. Prior to Mountain Lion I was allocating memory in my app that was roughly equivalent to free + inactive RAM. And it used to work perfectly, i.e. most inactive RAM used to become free. But in Mountain Lion, aggressive allocations are not affecting RAM at all. I want this util to also work on systems that don't have Xcode installed. I saw the post where someone posted notes of purge disassembly. But that isn't leading anywhere. Also purge comes with Xcode only. There are apps on Mac App Store that do this kind of thing. How to go about it? Any pointers would be really appreciated. Wishes, Nick ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On 6 Nov 2012, at 11:01, Nick Rogers roger...@mac.com wrote: Hi, Thanks for the replies. I was trying to achieve what essentially free memory apps on the Mac AppStore do. The RAM usage can be divided into four parts as shown in Activity Monitor. 1. Free 2. In-active 3. Active 4. Wired When I used my earlier app to allocate memory equal to free + inactive bytes, for the execution of the program it used to make the system less responsive for a few seconds and on release and quitting the app, most of the inactive memory would shift under free. e.g. if free is 1GB and inactive is 1.5GB, then after run, free would be 2.45GB and inactive just 50MB. Why on earth would you want to release inactive memory? This is memory that is in use by applications, just ones that haven't been scheduled in for a while. This RAM IIRC is automatically paged out to disk, so that if it is needed it can simply be overwritten, just like free memory, but has the side benefit that if it's not overwritten, then the inactive applications can be brought back to life very fast. Freeing it all would not gain anything, but would cause inactive apps to take much longer to return to the foreground. As an aside - free memory is a bad thing – having free memory means your system is not using all the RAM it has available to make things nice and fast. I fully expect my machine to use free memory for things like disk caches if I currently do not need the RAM for applications. Tom Davie ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
Again, if you want to clear cached memory on disk, issue a shell purge. All that other memory is being used for something. On Nov 6, 2012, at 6:01 AM, Nick Rogers wrote: Hi, Thanks for the replies. I was trying to achieve what essentially free memory apps on the Mac AppStore do. The RAM usage can be divided into four parts as shown in Activity Monitor. 1. Free 2. In-active 3. Active 4. Wired When I used my earlier app to allocate memory equal to free + inactive bytes, for the execution of the program it used to make the system less responsive for a few seconds and on release and quitting the app, most of the inactive memory would shift under free. e.g. if free is 1GB and inactive is 1.5GB, then after run, free would be 2.45GB and inactive just 50MB. Thanks again, Nick ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
Le 6 nov. 2012 à 12:13, Tom Davie tom.da...@gmail.com a écrit : On 6 Nov 2012, at 11:01, Nick Rogers roger...@mac.com wrote: Hi, Thanks for the replies. I was trying to achieve what essentially free memory apps on the Mac AppStore do. The RAM usage can be divided into four parts as shown in Activity Monitor. 1. Free 2. In-active 3. Active 4. Wired When I used my earlier app to allocate memory equal to free + inactive bytes, for the execution of the program it used to make the system less responsive for a few seconds and on release and quitting the app, most of the inactive memory would shift under free. e.g. if free is 1GB and inactive is 1.5GB, then after run, free would be 2.45GB and inactive just 50MB. Why on earth would you want to release inactive memory? This is memory that is in use by applications, just ones that haven't been scheduled in for a while. This RAM IIRC is automatically paged out to disk, so that if it is needed it can simply be overwritten, just like free memory, but has the side benefit that if it's not overwritten, then the inactive applications can be brought back to life very fast. The memory is paged out to disk only if it is read-write memory that was modified, and is not already on the disk. All mapped frameworks, the full content of the Unified Buffer Cache (which generally represent most of the inactive memory) and other stuff are keep in RAM to provide faster access, but are already present on disk and will be simply discarded if the system need more RAM. So not only freeing inactive memory is useless, but it is also guarantee to make your system slower. Freeing it all would not gain anything, but would cause inactive apps to take much longer to return to the foreground. As an aside - free memory is a bad thing – having free memory means your system is not using all the RAM it has available to make things nice and fast. I fully expect my machine to use free memory for things like disk caches if I currently do not need the RAM for applications. Tom Davie ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/devlists%40shadowlab.org This email sent to devli...@shadowlab.org -- Jean-Daniel ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 9:23 AM, Jean-Daniel Dupas wrote: Le 6 nov. 2012 à 12:13, Tom Davie tom.da...@gmail.com a écrit : On 6 Nov 2012, at 11:01, Nick Rogers roger...@mac.com wrote: Hi, Thanks for the replies. I was trying to achieve what essentially free memory apps on the Mac AppStore do. The RAM usage can be divided into four parts as shown in Activity Monitor. 1. Free 2. In-active 3. Active 4. Wired When I used my earlier app to allocate memory equal to free + inactive bytes, for the execution of the program it used to make the system less responsive for a few seconds and on release and quitting the app, most of the inactive memory would shift under free. e.g. if free is 1GB and inactive is 1.5GB, then after run, free would be 2.45GB and inactive just 50MB. Why on earth would you want to release inactive memory? This is memory that is in use by applications, just ones that haven't been scheduled in for a while. This RAM IIRC is automatically paged out to disk, so that if it is needed it can simply be overwritten, just like free memory, but has the side benefit that if it's not overwritten, then the inactive applications can be brought back to life very fast. The memory is paged out to disk only if it is read-write memory that was modified, and is not already on the disk. All mapped frameworks, the full content of the Unified Buffer Cache (which generally represent most of the inactive memory) and other stuff are keep in RAM to provide faster access, but are already present on disk and will be simply discarded if the system need more RAM. So not only freeing inactive memory is useless, but it is also guarantee to make your system slower. Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB. Plus, if you're booting off, or have your swap file on an SSD disk related performance penalties will be much less than if using an HD to hold the swap file. OK, yes, it will be slower, but it might not be noticeable. And from what I've seen, many web site creators aren't treating each of their pages as if they should be memory controlled. Turning off JavaScript certainly prevents much of this bloat. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 7:08 AM, Alex Zavatone z...@mac.com wrote: Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB If that actually gets you back memory, it’s just because Safari has marked some of its allocated address space as ‘purgeable’. You would have gotten that space back if it became necessary anyway, without the need to do anything explicit, because the kernel will start tossing out purgeable address space as needed to free up space for new allocations. The basic principle is, don’t second-guess the kernel, at least not unless you know its architecture really well or have read through Singh’s “Mac OS X Internals” book :) In my experience, Activity Monitor’s pie charts of system memory usage are nice as blinkenlights but nearly useless for any practical purpose of mine. —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 3:01 AM, Nick Rogers roger...@mac.com wrote: I was trying to achieve what essentially free memory apps on the Mac AppStore do. Those apps are useless, except as revenue generators for their authors. When I used my earlier app to allocate memory equal to free + inactive bytes, for the execution of the program it used to make the system less responsive for a few seconds and on release and quitting the app, most of the inactive memory would shift under free. That doesn’t serve any useful purpose (it just slows down the OS), _unless_ you are trying to profile a cold launch of an app at system startup, i.e. see how your app performs when none of its code or data are possibly still cached. And in that case the ‘purge’ command will do the job. —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On 6 Nov 2012, at 11:30 AM, Jens Alfke j...@mooseyard.com wrote: On Nov 6, 2012, at 7:08 AM, Alex Zavatone z...@mac.com wrote: Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB If that actually gets you back memory, it’s just because Safari has marked some of its allocated address space as ‘purgeable’. You would have gotten that space back if it became necessary anyway, without the need to do anything explicit, because the kernel will start tossing out purgeable address space as needed to free up space for new allocations. The basic principle is, don’t second-guess the kernel, at least not unless you know its architecture really well or have read through Singh’s “Mac OS X Internals” book :) In my experience, Activity Monitor’s pie charts of system memory usage are nice as blinkenlights but nearly useless for any practical purpose of mine. I understand that this is what is supposed to happen, and I do believe that smart people with good intentions have worked to make it happen. But it often happens that when Activity Monitor's pie chart shows no free RAM, my computer becomes sluggish. It rarely happens that when my computer is sluggish, Activity Monitor shows free RAM. It's not 1:1, and maybe I'm a victim of confirmation bias, but that's my experience. — F ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 8:08 AM, Alex Zavatone z...@mac.com wrote: On Nov 6, 2012, at 9:23 AM, Jean-Daniel Dupas wrote: Le 6 nov. 2012 à 12:13, Tom Davie tom.da...@gmail.com a écrit : On 6 Nov 2012, at 11:01, Nick Rogers roger...@mac.com wrote: Hi, Thanks for the replies. I was trying to achieve what essentially free memory apps on the Mac AppStore do. The RAM usage can be divided into four parts as shown in Activity Monitor. 1. Free 2. In-active 3. Active 4. Wired When I used my earlier app to allocate memory equal to free + inactive bytes, for the execution of the program it used to make the system less responsive for a few seconds and on release and quitting the app, most of the inactive memory would shift under free. e.g. if free is 1GB and inactive is 1.5GB, then after run, free would be 2.45GB and inactive just 50MB. Why on earth would you want to release inactive memory? This is memory that is in use by applications, just ones that haven't been scheduled in for a while. This RAM IIRC is automatically paged out to disk, so that if it is needed it can simply be overwritten, just like free memory, but has the side benefit that if it's not overwritten, then the inactive applications can be brought back to life very fast. The memory is paged out to disk only if it is read-write memory that was modified, and is not already on the disk. All mapped frameworks, the full content of the Unified Buffer Cache (which generally represent most of the inactive memory) and other stuff are keep in RAM to provide faster access, but are already present on disk and will be simply discarded if the system need more RAM. So not only freeing inactive memory is useless, but it is also guarantee to make your system slower. Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB. Plus, if you're booting off, or have your swap file on an SSD disk related performance penalties will be much less than if using an HD to hold the swap file. Memory remains the target of much superstition. The OS will take care of managing memory--you don't need to do it. Common utilities like Activity Monitor and Task Manager have given micro-managing users an excuse to second-guess their OS, which is rarely wise. Preston ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 1:13 PM, William Sumner wrote: On Nov 6, 2012, at 8:08 AM, Alex Zavatone z...@mac.com wrote: Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB. Plus, if you're booting off, or have your swap file on an SSD disk related performance penalties will be much less than if using an HD to hold the swap file. Memory remains the target of much superstition. The OS will take care of managing memory--you don't need to do it. Common utilities like Activity Monitor and Task Manager have given micro-managing users an excuse to second-guess their OS, which is rarely wise. Preston The only reason I resorted to this was because of performance issues. If Safari is running, and a large amount of memory is used up, it's most likely in pages or images that are running in Safari that are behind what I am looking at. Many might be images that have come and gone that are not needed by pages any more, but according to the memory model, they are still needed. But, as the user of the system, I don't care, unless Safari is in the foreground and I am looking at the page/tab which needs allocated items. This is where a purge is useful. I'm telling the system to push away the items that I don't care about. At times, I have tested issuing a SIGSTOP and a SIGCONT to Safari as the app goes to the goes to the background and comes to the front and simply by pausing the app, performance on my system (quad core i7 MBP, 16 GB RAM, 480 GB SSD) improves. The GUI becomes more snappy. This also happens when temporarily disabling JavaScript. Also, there is some interaction between dock widgets and Safari that I don't understand that is related to performance and memory where if I kill the dock, performance of the whole system picks up and the Activity Monitor blinkenlights memory readout frees up a few gig. In fact I just issued a purge and got about a gig back from Safari. Sure, it's running and items are allocated as being used, but all of that isn't needed at once. I find that, at least when Safari and webkit is involved, the OS's memory management doesn't take in to effect that many of the opened windows and tabs do not need to have the same high priority as other applications and memory management doesn't handle making non front pages and tabs second class citizens fast enough. Just my experience though. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 1:05 PM, Fritz Anderson wrote: On 6 Nov 2012, at 11:30 AM, Jens Alfke j...@mooseyard.com wrote: On Nov 6, 2012, at 7:08 AM, Alex Zavatone z...@mac.com wrote: Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB If that actually gets you back memory, it’s just because Safari has marked some of its allocated address space as ‘purgeable’. You would have gotten that space back if it became necessary anyway, without the need to do anything explicit, because the kernel will start tossing out purgeable address space as needed to free up space for new allocations. The basic principle is, don’t second-guess the kernel, at least not unless you know its architecture really well or have read through Singh’s “Mac OS X Internals” book :) In my experience, Activity Monitor’s pie charts of system memory usage are nice as blinkenlights but nearly useless for any practical purpose of mine. I understand that this is what is supposed to happen, and I do believe that smart people with good intentions have worked to make it happen. But it often happens that when Activity Monitor's pie chart shows no free RAM, my computer becomes sluggish. It rarely happens that when my computer is sluggish, Activity Monitor shows free RAM. It's not 1:1, and maybe I'm a victim of confirmation bias, but that's my experience. — F Exactly the same condition happens here, which is why I ended up resorting to the purge command. Most (all) of the memory bloat and performance problems that come with it that I have on my system is due to Safari and I've narrowed it down to a few things previously mentioned. If only I could get in the habit of using another browser. Even with disabling Flash and as many superfluous graphics, it's still the #1 memory pig on my system. Disabling Javascript certainly helps. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On 06.11.2012, at 12:01, Nick Rogers roger...@mac.com wrote: I was trying to achieve what essentially free memory apps on the Mac AppStore do. The RAM usage can be divided into four parts as shown in Activity Monitor. You're aware that those applications are snake oil, right? There is no practical benefit to clearing free RAM. It will actually make things slower. Cheers, -- Uli Kusterer The Witnesses of TeachText are everywhere... http://www.masters-of-the-void.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On 06.11.2012, at 16:08, Alex Zavatone z...@mac.com wrote: Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB. Plus, if you're booting off, or have your swap file on an SSD disk related performance penalties will be much less than if using an HD to hold the swap file. Err ... if I understand correctly, you're nuking the caches used by the system and other applications to compensate for the problem that Safari, when left open, leaks like a sieve ... ? Those two things are orthogonal. Cheers, -- Uli Kusterer The Witnesses of TeachText are everywhere... http://www.masters-of-the-void.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
Well, yes, maybe. If the Mac is booted from an SSD, and the system performance starts to lag or memory starts to get full, I'll gladly purge the cache since paging out to SSD again isn't as much of a time consuming task. If I were able to target Safari and its processes (WebProcess), then I'd do that. Actually, I don't think that what I'm seeing are Safari/Webkit leaks - unless you know otherwise. I think the people who are creating pages that are loaded in Safari are the villains and are not freeing up allocated variables, but I have gotten particular pages in Safari where certain operations are blocking the thread and as soon as that page is closed, my whole system becomes snappier. In my cursory understanding of what's going on beneath the hood, that shouldn't happen at all but it does. I've never seen FireFox, Camino or Chrome crater the performance of my Mac like Safari does but, I agree, this is outside of the original discussion. Ideally when this happens, I'd love to save my list of pages I'm interested in and either restart Safari with only those URLs, or fire up another browser and load that list of URLs in a queue. On Nov 6, 2012, at 2:41 PM, Uli Kusterer wrote: On 06.11.2012, at 16:08, Alex Zavatone z...@mac.com wrote: Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB. Plus, if you're booting off, or have your swap file on an SSD disk related performance penalties will be much less than if using an HD to hold the swap file. Err ... if I understand correctly, you're nuking the caches used by the system and other applications to compensate for the problem that Safari, when left open, leaks like a sieve ... ? Those two things are orthogonal. Cheers, -- Uli Kusterer The Witnesses of TeachText are everywhere... http://www.masters-of-the-void.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 12:58 PM, Alex Zavatone wrote: Ideally when this happens, I'd love to save my list of pages I'm interested in and either restart Safari with only those URLs Close the pages you're not interested in, quit Safari, launch Safari, choose History - Reopen All Windows from Last Session. Unless of course pages you're interested in include ones where you've had to log in to the site... -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 3:25 PM, Jack Carbaugh intrn...@me.com wrote: Facebook is a safari killer. if left open, it will bring down a system. And by bring down I mean, make it so unresponsive that the only option is a forced reboot via power button. It happened everyday on my other half's clean system, until i set up automatic log off. (He could never remember to just close the tab.) On Nov 6, 2012, at 2:41 PM, Uli Kusterer witness.of.teacht...@gmx.net wrote: On 06.11.2012, at 16:08, Alex Zavatone z...@mac.com wrote: Actually, that's not always the case. As I use Safari through out the day, Safari ends up eating 6 to 12 GB of data on my 16 GB system. Frequently, I need to issue a purge to get back a spare GB or few hundred MB. Plus, if you're booting off, or have your swap file on an SSD disk related performance penalties will be much less than if using an HD to hold the swap file. Err ... if I understand correctly, you're nuking the caches used by the system and other applications to compensate for the problem that Safari, when left open, leaks like a sieve ... ? Those two things are orthogonal. Cheers, -- Uli Kusterer The Witnesses of TeachText are everywhere... http://www.masters-of-the-void.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/intrntmn%40aol.com This email sent to intrn...@aol.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
Facebook is a safari killer. if left open, it will bring down a system. And by bring down I mean, make it so unresponsive that the only option is a forced reboot via power button. It happened everyday on my other half's clean system, until i set up automatic log off. (He could never remember to just close the tab.) ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 6, 2012, at 11:58 AM, Alex Zavatone z...@mac.com wrote: Ideally when this happens, I'd love to save my list of pages I'm interested in and either restart Safari with only those URLs, or fire up another browser and load that list of URLs in a queue. Uh, you do realize in Lion and later, this is supported as application restore? Something happened around the Safari 6.0 release which caused this piggy behavior. Sometimes Safari crashes, and sometimes I just quit it and start over. This lasts about a day or so with nothing else happening—especially without plugins or Java activated. Really, that's the only way to fix this without actually fixing Safari. Otherwise, keep submitting bugs to Apple. Hopefully someone will do something. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/ ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
a way to clear inactive RAM
Hi, I am assigned this small utility which should clear inactive RAM. I know Mac OS X manages memory quite efficiently and inactive RAM also has a purpose. But I have to make this. Prior to Mountain Lion I was allocating memory in my app that was roughly equivalent to free + inactive RAM. And it used to work perfectly, i.e. most inactive RAM used to become free. But in Mountain Lion, aggressive allocations are not affecting RAM at all. I want this util to also work on systems that don't have Xcode installed. I saw the post where someone posted notes of purge disassembly. But that isn't leading anywhere. Also purge comes with Xcode only. There are apps on Mac App Store that do this kind of thing. How to go about it? Any pointers would be really appreciated. Wishes, Nick ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On Nov 5, 2012, at 10:54 AM, Nick Rogers roger...@mac.com wrote: I am assigned this small utility which should clear inactive RAM. I know Mac OS X manages memory quite efficiently and inactive RAM also has a purpose. But I have to make this. What on earth does “clear inactive RAM” mean? No offense, but whoever assigned you that task doesn’t seem to have any idea of how a modern virtual memory system works. What do they want this utility to accomplish? Regardless, this isn’t the right list for such a question. There aren’t Cocoa/Obj-C APIs for anything that low level, so if you want to mess with paging and swap files and virtual memory, you’ll need to use POSIX or Mach functions. Try the “darwin-userlevel” list. —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
On 5 Nov 2012, at 10:54 AM, Nick Rogers wrote: I am assigned this small utility which should clear inactive RAM. I know Mac OS X manages memory quite efficiently and inactive RAM also has a purpose. But I have to make this. What are you trying to achieve? What exactly do you mean by inactive? There may be a higher-level way to reach the same goal. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: a way to clear inactive RAM
Not sure what RAM clearing means but if you want to purge the disk cache, check out man purge in the terminal. On Nov 5, 2012, at 1:54 PM, Nick Rogers wrote: Hi, I am assigned this small utility which should clear inactive RAM. I know Mac OS X manages memory quite efficiently and inactive RAM also has a purpose. But I have to make this. Prior to Mountain Lion I was allocating memory in my app that was roughly equivalent to free + inactive RAM. And it used to work perfectly, i.e. most inactive RAM used to become free. But in Mountain Lion, aggressive allocations are not affecting RAM at all. I want this util to also work on systems that don't have Xcode installed. I saw the post where someone posted notes of purge disassembly. But that isn't leading anywhere. Also purge comes with Xcode only. There are apps on Mac App Store that do this kind of thing. How to go about it? Any pointers would be really appreciated. Wishes, Nick ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
