Beavis, I'm ashamed of you advising this! 
We have an excellent Beta Testing team that beats us to death until we get everything down. Sometimes, for MTU reasons, we must do a release with a known bug still in it. Gee.... and Microsoft had how many million bugs in Windows?
Beavis, if you always wait for the "second next" release to come out, you are still running with bugs that were fixed in the next release.
Read the bugs we fixed in 3.313 that were reported in 3.312. All those who reported them are very happy with 3.313, and as you can see in this post, there many who don't see your problem. The VAST MAJORITY of users are running fine.
The problem reported in this thread is a SYSTEM RELATED BUG. It is clear it is a bug, but it is also clear that only a very few are experiencing it. Those of you who are, yes, roll back to 3.312 as for you it is an unacceptable bug.
But Beavis... get outta here with your "don't upgrade" advice! 
If everyone followed that, we'd never find problems like this one.
As kilith clearly restated the same thing I had stated earlier, we need facts.
Everyone, read your posts. EMOTIONS... EMOTIONS... EMOTIONS. No facts. Stop the "agreeing with each other" posts that waste everyone's time, and post whatever facts you can bombard us with (we NEVER have too many facts). Then, maybe from the cumulative set of facts a picture will become clear where to look.
Hoster 3.314 will be the next project we are on in 2007. If we don't have any facts from those of you who are experiencing the problem,
it won't be fixed in 3.314 either! 
The NEXT release will be Hoster 4.0, which will be many months off. I hope that's enough incentive to get you to post your facts! 