We're on XP 32 bit with 3GB of RAM and it's definately not a hung save. It has happened three times, so each time we've "reinforced" our STC protocols.
We get two messages. One is the busy popup and the other states that the file we're tyring to synchronise is an incompatable version.
Our reseller has suggested that:
A) The Central File keeps track of each and every local file that ever gets created and tries to ping them for changes. When you re-create the Central it starts over with a new list and performance improves. So, we should make on local and stick with it.
B) Overwriting local files compounds the issue because the Central file is now looking for two files with the same name where only one exists. (opening two sessions of Revit with the same user name bypasses the rights management and results in an irreconilable local so I can see where overwriting locals might confuse the Central)
C) The 2010 feature for creating a new Local from Central does open the central file for a brief moment while it creates the local. I was thinking it was copyinig in the background and then opening, so I'm a little uncomfortable with that feature now.
Net-net: We are going to try using the old fashioned copy-paste-rename technique of making Local files and have users refrain from making new locals each day, which was the previous best practice.