The Explorer: Resource Leaks, Part Three

Step Five: Clean Up After Spills
The freeware RAMpage memory optimizer, RAMpage, has a command-line-driven "run once then exit" mode. I've coded the command-line parameters into a batch file, and run RAMpage after some other application crashes: RAMpage loads, does its thing (including trying to recover "orphaned" memory left by the crashed app) and then exits. I'd never leave RAMpage (or any memory optimizer) running all the time due to the problems listed in the previous column, But as a simple, free way to try to clean up after an app does crash (and thus possibly avoid the need to reboot) it seems to work pretty well.

You can set up the batch file any way you like. But if it'll help, the step-by-step method I use is available here.

Why Some Systems Are More Stable Than Others
I think the five steps above are the key to why some systems seem to run forever, are rock solid, and suffer none or trivial resource leaks; while others are memory sieves that have to be rebooted on a regular and routine basis. The systems that run good apps to start with; and that also have their entire memory system tuned to perfection; and that clean up after mishaps; are the stable ones.

If your system isn't as stable as you'd like, get rid of the bad software, take control of your swapfile and Vcache settings, align your apps, and then clean up after crashes. Chances are you'll achieve a whole new level of stability that you never thought possible!

To discuss this column with other readers, please visit Fred Langa's forum on the Listening Post.

To find out more about Fred Langa, please visit his page on the Listening Post.