Clean your RAM with Alfred

[PixelPaul]

Hey,

 

i've made a workflow for cleaning your RAM. Type in 'clean ram' or 'purge' and press enter.

 

https://www.dropbox.com/s/a8drgdbwypygmmk/Clean%20RAM.alfredworkflow

 

Hope you find it as usefull as i do.

 

Edited: Terminal command works in background. When RAM is cleaned, a notification pops up.

Edited August 2, 2013 by PixelPaul

[vitor]

You should exchange Terminal Command for Run Script — there’s no reason a terminal should need to open for this.

[PixelPaul]

Thanks, changed it.

[Southgirl]

As no notification pops up, is there any other way to tell if this is actually working?

[getthething]

Have all the clean RAM workflows stopped working for anyone else since upgrading to Mavericks?

[Tyler Eich]

Have all the clean RAM workflows stopped working for anyone else since upgrading to Mavericks?

 

In Mavericks, the purge command requires super user privileges. So if a workflow uses purge instead of sudo purge, the script will fail. However, using sudo purge will not work directly because sudo cannot prompt you for your password from a 'Run Script' object.

 

One workaround I found is to change the 'Run Script' language to '/usr/bin/osascript'. Then, use 

do shell script "purge" with administrator privileges

 in the text area. It will prompt for your password and the command will execute once provided.

 

OS X Daily helped me solve this issue. The linked post makes a few notes about Mavericks' memory management, as well.

Edited December 14, 2013 by Tyler Eich

[getthething]

In Mavericks, the purge command requires super user privileges. So if a workflow uses purge instead of sudo purge, the script will fail. However, using sudo purge will not work directly because sudo cannot prompt you for your password from a 'Run Script' object.

 

One workaround I found is to change the 'Run Script' language to '/usr/bin/osascript'. Then, use 

do shell script "purge" with administrator privileges

 in the text area. It will prompt for your password and the command will execute once provided.

 

OS X Daily helped me solve this issue. The linked post makes a few notes about Mavericks' memory management, as well.

Very thorough. Much appreciated. Thank you.