"...OS X has a feature called inactive memory. This is memory that was recently used by an app you closed and can be quickly made to active memory if you resume to use that app. A nice concept, that fails miserably. OS X's documentation says, that this memory may be freed at any moment. However in practice, it just keeps on accumulating until you run out of free memory. In this case a sane option for the OS would be freeing the inactive memory. Instead the OS X decides to swap the inactive memory on the disk. So when running out of free memory and having a 1.5 gigabytes of inactive memory left, your OS starts paging the unused inactive memory to disk instead of freeing it for applications to use. Not only this causes your computer to slow down, it also is counter-intuitive in the terms of the original idea of inactive memory: when it's on disk, it definitely is not made active quickly.
"I managed to find out that this memory can be freed with combination of XCode's purge-command and repairing disk permissions. First usually freed around 200MB of memory while latter freed almost every bit of inactive memory. Eventually this became a daily routine. When arriving to work the first thing was to hit repair disk permissions button and do something else than actually use the computer for the next five to ten minutes. Sigh...."
Um, yes. It doesn't do what the developer docs says it does, just as described in link. I've observed it myself. Yes, inactive decreases as well as increases over time, but immaterial to the fact that inactive still gets paged to disk — doesn't matter whether it's "only" modified inactive; *no* inactive should (defeats the purpose!). Watch the swap files pile up!... If it's a scam, then why does my excruciating sluggishness go away when running FreeMemory-type utilities (or purge in Terminal)? Without them, I'd have to go back to rebooting every time this happens.
Yes, I'm sure. I've personally observed the undesirable behavior at least as far back as 10.4 Tiger.... Inactive should *never* be paged to disk, no matter what TheWormyFruit™'s docs say; to repeat, it defeats the purpose and the thrashing unnecessarily slows down the Mac.... Linux & other Unix-type OS apparently don't do this for the most part, it's all Apple arrogance... Some of the heavy-lifting things you described you do themselves may be purging inactive as you use them, similar to what FreeMemory-type utilities or repairing permissions do.... Nevertheless, it's not consistent & many Macs don't overtly experience it — sometimes there seems no rhyme or reason to it.... In any event, the acid test is that when one *does* chronically experience it, and purging inactive by any means (or rebooting to do so) restores robustness, I'm going to keep doing it, so I can get some work done instead of fighting the goddamned computer.
"...OS X has a feature called inactive memory. This is memory that was recently used by an app you closed and can be quickly made to active memory if you resume to use that app. A nice concept, that fails miserably. OS X's documentation says, that this memory may be freed at any moment. However in practice, it just keeps on accumulating until you run out of free memory. In this case a sane option for the OS would be freeing the inactive memory. Instead the OS X decides to swap the inactive memory on the disk. So when running out of free memory and having a 1.5 gigabytes of inactive memory left, your OS starts paging the unused inactive memory to disk instead of freeing it for applications to use. Not only this causes your computer to slow down, it also is counter-intuitive in the terms of the original idea of inactive memory: when it's on disk, it definitely is not made active quickly.
"I managed to find out that this memory can be freed with combination of XCode's purge-command and repairing disk permissions. First usually freed around 200MB of memory while latter freed almost every bit of inactive memory. Eventually this became a daily routine. When arriving to work the first thing was to hit repair disk permissions button and do something else than actually use the computer for the next five to ten minutes. Sigh...."
Make an AppleScript applet containing only one line:
do shell script "purge"
Save it as an "Application Bundle" (for Intel Macs; otherwise, saved as an "Application" will want Rosetta, and not run at all under Lion), and just double-click it whenever you want to free up RAM.
Version 3.201 no longer is freeware, but now is shareware.
Only a crippled subset of features can be used without purchase and registering with a serial number.
According to the "More Information" webpage, v1.9.5a is for "Snow Leopard or higher."
A more general complaint, I don't know who designates the "Requirements" - MacUpdate.com or the publisher - but it's gotten to be utterly unreliable: I always have to go to the publisher's website to see what the minimum OS requirement actually is, because the MacUpdate page gets it wrong so often. MacUpdate needs to address this problem.
This MacUpdate page for VLC Media Player 1.0.2 has an additional download link for Tiger users:
"Version 0.9.9a for Mac OS X 10.4"
But the VideoLAN - VLC media player main website:
http://www.videolan.org/
...has a newer version 0.9.10, about which it says, "This version mostly targets the Mac OS X 10.4 platform. It includes various improvements and bugfixes for this port as well as updates to access, stream out and decoder modules plus certain third party libraries. The integer underflow fix from VLC 1.0.1 is also included."
Hope a MacUpdate moderator investigates this and makes any necessary changes to the above possibly outdated link.
What exactly does this app do?
Am I to understand that all it does is be an app that has a short menu bar, so that if one has a lot of menu extras, they otherwise won't be covered up by apps with long menu bars?
Library not loaded: @executable_path/rbframework.dylib
Referenced from: ~/Desktop/SyncTwoFolders.app/Contents/MacOS/SyncTwoFolders
Reason: image not found
+1
Anti Flashback Trojan
-1
FreeMemory
Completely failed memory management in Mac OSuX
"...OS X has a feature called inactive memory. This is memory that was recently used by an app you closed and can be quickly made to active memory if you resume to use that app. A nice concept, that fails miserably. OS X's documentation says, that this memory may be freed at any moment. However in practice, it just keeps on accumulating until you run out of free memory. In this case a sane option for the OS would be freeing the inactive memory. Instead the OS X decides to swap the inactive memory on the disk. So when running out of free memory and having a 1.5 gigabytes of inactive memory left, your OS starts paging the unused inactive memory to disk instead of freeing it for applications to use. Not only this causes your computer to slow down, it also is counter-intuitive in the terms of the original idea of inactive memory: when it's on disk, it definitely is not made active quickly.
"I managed to find out that this memory can be freed with combination of XCode's purge-command and repairing disk permissions. First usually freed around 200MB of memory while latter freed almost every bit of inactive memory. Eventually this became a daily routine. When arriving to work the first thing was to hit repair disk permissions button and do something else than actually use the computer for the next five to ten minutes. Sigh...."
http://dywypi.org/2012/02/back-on-linux.html
+2
+2
-1
FreeMemory Pro
"...OS X has a feature called inactive memory. This is memory that was recently used by an app you closed and can be quickly made to active memory if you resume to use that app. A nice concept, that fails miserably. OS X's documentation says, that this memory may be freed at any moment. However in practice, it just keeps on accumulating until you run out of free memory. In this case a sane option for the OS would be freeing the inactive memory. Instead the OS X decides to swap the inactive memory on the disk. So when running out of free memory and having a 1.5 gigabytes of inactive memory left, your OS starts paging the unused inactive memory to disk instead of freeing it for applications to use. Not only this causes your computer to slow down, it also is counter-intuitive in the terms of the original idea of inactive memory: when it's on disk, it definitely is not made active quickly.
"I managed to find out that this memory can be freed with combination of XCode's purge-command and repairing disk permissions. First usually freed around 200MB of memory while latter freed almost every bit of inactive memory. Eventually this became a daily routine. When arriving to work the first thing was to hit repair disk permissions button and do something else than actually use the computer for the next five to ten minutes. Sigh...."
http://dywypi.org/2012/02/back-on-linux.html
+2
+3
ColorWell
choose color
...and save as an Application bundle.
+2
MemoryFreer
do shell script "purge"
Save it as an "Application Bundle" (for Intel Macs; otherwise, saved as an "Application" will want Rosetta, and not run at all under Lion), and just double-click it whenever you want to free up RAM.
-2
Phone to Mac
Only a crippled subset of features can be used without purchase and registering with a serial number.
+1
TiVoDesktop
A more general complaint, I don't know who designates the "Requirements" - MacUpdate.com or the publisher - but it's gotten to be utterly unreliable: I always have to go to the publisher's website to see what the minimum OS requirement actually is, because the MacUpdate page gets it wrong so often. MacUpdate needs to address this problem.
+1
VLC Media Player
"Version 0.9.9a for Mac OS X 10.4"
But the VideoLAN - VLC media player main website:
http://www.videolan.org/
...has a newer version 0.9.10, about which it says, "This version mostly targets the Mac OS X 10.4 platform. It includes various improvements and bugfixes for this port as well as updates to access, stream out and decoder modules plus certain third party libraries. The integer underflow fix from VLC 1.0.1 is also included."
Hope a MacUpdate moderator investigates this and makes any necessary changes to the above possibly outdated link.
Menuola
Am I to understand that all it does is be an app that has a short menu bar, so that if one has a lot of menu extras, they otherwise won't be covered up by apps with long menu bars?
AudioFaucet
SizeWell
~/Library/Application Support/SIMBL/Plugins/SizeWell.bundle
- Already had SIMBL 0.8.2 for my Leopard 10.5.8 here:
/Library/InputManagers/SIMBL/SIMBL.bundle
- Quit Finder and relaunched.
Resizing a window with any of the command key combinations doesn't produce the desired results; just resizes the window normally.
Suggestions?
-1
SyncTwoFolders
**********
Host Name: Schmye-Bubbulas-Computer
Date/Time: 2009-04-05 12:33:10.520 -0400
OS Version: 10.4.9 (Build 8P135)
Report Version: 4
Command: SyncTwoFolders
Path: ~/Desktop/SyncTwoFolders.app/Contents/MacOS/SyncTwoFolders
Parent: WindowServer [67]
Version: v.1.3.5 (1.3.5)
PID: 14230
Thread: Unknown
Link (dyld) error:
Library not loaded: @executable_path/rbframework.dylib
Referenced from: ~/Desktop/SyncTwoFolders.app/Contents/MacOS/SyncTwoFolders
Reason: image not found
-1
+2