Originally posted by RichardH
For what it's worth, I used to have various random weird issues that rose up and reared their ugly heads in a variety of problems, ranging from kernel panics to strange hangs.
Flakey RAM (or other hardware) often causes that random misbehavior. Of course it's sometimes software-related, as you discovered:
I did exactly one thing a while ago (6+ months, so it may no longer pertain to current versions and I don't want to dis the developer(s) of what appear to be pretty cool, but not exactly essential programs and m0dz), I removed all the Unsanity haxies and the APE Application Framework.
Presto. All the weirdness went away.
I like the APE framework and many of the haxies are highly neato. But I just don't have the time to dick around searching for obscure problems with no apparent resolution -- or waiting for another .dot update from UnSanity every time a new 10.4.x release arrives -- I need to USE my computers, like, NOW.
This is sorta a bummer since some cool programs depend on the APE framework for additional functionality, but the positives far outweigh the negatives in this case, for me anyway.
If you're not
using APE I think you want to invert "positives" and "negatives" for that final sentence to make sense.
For me, the potential negative risks of running APE+haxies still outweigh the positive benefits. I tinkered with them a bit in 10.1/10.2 but with every major OS X update I've gotten more conservative with what end up reinstalling from the previous release. Experience has tamed my necessities; a fast Tiger is more satisfying than a fat one.
I've run CodeTek VirtualDesktop for a few years and have never noticed any system instability caused by its use of mach_inject
. All of my rare kernel panics have been hardware-related.