Bug Stability and editor issues with R3 that are impossible/hard to repro.

Hi,
Unity has been having a lot of repeat issues that our team isn't able to repro with the latest release candidate. These issues are not bug-able with re-producible steps due to their frequency and/or fact that they eventually fix themselves. These issues are experienced by all our team members on multiple rigs and setups.

1) The Latest R3 Editor has become so slow on some computers that it is unusable. (A bug was opened on this issue)

2) Nested prefabs occasionally lose references to other nested prefabs. The guid of the object the reference is pointing to will have been unchanged and will not be lost from all prefabs assets. We cannot determine a pattern or find any evidence of changed guids in SVN. Our belief is that changing a parent prefab will sometimes temporally change a child prefab in a way where other prefabs currently in scene can lose references to that object.

3) Unity is not updating or detecting changes properly. Often after syncing and reloading unity it will not detect the changes. For example, a team member will change a material on one computer and check it in. We will sync another computer and launch unity. The material changes will not be present. The only way we can get Unity to update in these cases is to delete a material and meta file (not necessarily the material that changed) and re-sync files. Then unity will update. Just restarting unity does not fix the issue. Deleting libraries does.

4) Unity sometimes jumps to new folders in the project window when selecting objects in the hierarchy. The folders it jumps to are unrelated to the object selected.

5) You can not always rename objects in the hierarchy, unity will un-select them as you type. This issue happens randomly.

6) Unity is now causing visual studio to reload when nothing was changed but when a script is double clicked. This happens frequently and is drastically slowing down workflows where people go from editor to VS and back again quickly.

7) When autosaving prefabs if you QUICKLY hit play after making a change. The game will sometimes get a null reference error to that prefab while running. If you stop playing and then hit play again the game will run properly. It is possible that some objects may have lost references to the prefab that failed to save in this instance though. In those cases you must revert.