Just so everybody knows, when a program has a serious bug that takes a long time to figure out, fixing it may have to be done at a very low level. And since the fix is at that level it may cause other things to break. The nice thing is that those other things that break are usually much easier to find and fix since the original error was so deep in the system AND the programmer(s) know what they changed at the lower level and have a better grasp of how things are dependent on that spot.
It's like your car has a problem running. You look and look and eventually find a slightly bent crank shaft. Bad, bad, bad as that means you are burning a lot more gas, your engine is running a lot hotter, and so on. But before you discovered the real source of your problems you adjusted the fuel mixture to compensate for the gas consumption, adjusted the cooling system to make the whole thing run cooler, and so on and so on. Now that you've fixed the real problem it takes you a while to fix the previous fixes you did before you found out the real problem.
So don't be surprised if the road's a little rough for the next month or so with strange things happening. More than likely they'll get remedied pretty fast.
That's my take on it, anyway.
AJ