Unity Completely Unresponsive After OSX Update

  • iMac
  • OSX 10.8.3
  • Unity 4.1.0f4
  • Spotlight off

…every action in Unity is met with the spinning rainbow circle, and at least 10 - 15 seconds before that action is executed. Meaning something as innocuous as selecting an object, focusing a window pane, etc.

Everything has actually been fine since the beginning of my Unity/Mac experience in 2009, this being the first productivity shattering event ever. Unity is unusable.

Order of events this past week:

  • Installed latest Unity3d 4.1.0f4
  • Installed latest XCode via Appstore
  • Installed latest OSX update via Appstore last night (I can’t seem to find an update history to see what was changed)
  • Turned off Spotlight this morning in the event that was the problem

Attempted to launch a variety of projects, from my own to asset store projects to Unity3D’s own projects…all same issue.

I’ve tried rebooting a few times…nada.

Rest of my computer is fine and every other program is responsive as expected. It’s only when I try to do something in Unity will the machine as a whole be affected, clearly pointing to a Unity issue.

I wouldn’t know how to submit a bug report only in that I have to Force Quit Unity, and I’m not certain that report would offer anything useful. Maybe?

Thoughts?

-Steve

Submitting a crash bug report is always appreciated. It can give us detailed information about what is causing the crash.

That’s just it. As I noted in my other thread:

…I’m not crashing thus no valuable data is available to submit.

Thanks Ant

-Steve

Oops! Just realized I got my threads confused!

Haha… :smile:

Thanks again Ethan

-Steve

I have the same issue… I uninstalled, removed anything related to Unity under preferences (~/Library/Preferences/), restarted and installed v4.0.1. It seems to have worked for me.

Can’t speak to 4.0.1, as my issue was with the latest Unity, 4.1.0f4.

Cheers

I had the issue on 4.1 then removed everything and reinstalled the older version.

Thats more clear Cavan, thanks. Yea I thought you were just uninstalling and reinstalling 4.0.1. :slight_smile:

-Steve