It started when I was reading the rules for crashing programs. I saw that crashing an OS forced a time consuming reboot, but any other program could simply be reloaded 3 seconds later. That hardly seems a fair trade for an extended test with a 1 combat turn interval. Maybe it would take 6 seconds: a simple action to deactivate and a complex to run the program again. Even that's not a fair trade. What's the point of even having rules for crashing programs? Then I had an idea. What if crashed programs were frozen and couldn't be deactivated? You could load a new instance, but the crashed program would just sit there taking up a slot in the system. At least then a hacker would have the satisfaction of affecting response (albeit slowly). And why just for the Crash Program action? Why shouldn't crashed Agents and IC also be frozen and hog resources? Of course they could all be cleared with a reboot.
The more I thought about it, the more I liked the idea. What's more frustrating than defeating the dreaded IC in cybercombat only to see it pop up again moments later with absolutely nothing to show for your hard work?
Now the questions for Dumpshock.
Is this a good idea? (At the moment I'm thinking they should errata or more likely FAQ it into effect.)

Is this fair? Will it change too much? Is it even worth the hassle? Will it change too little? Would this change your hacker's strategy in the Matrix? How?
Lastly, has this already been proposed and hashed over, or is this the way it already works? If so, sorry.

I'll be back after a good days sleep to see how much y'all hated this!