A number of times I’ve had Unity 3.5 (Mac version) lock up on me, forcing me to ‘Force Quit’ the application and restart. On two occasions, I’ve actually had it lock up (freeze) my entire machine, forcing me to hard reset and reboot.
I can’t pinpoint what’s causing it, as it appears to be random.
However, the two times it’s completely frozen my machine I’ve been running the game scene in the ‘Game’ window, and at the same time I’ve been editing values or dragging objects or particles around the scene.
Never had an issue with 3.4.2.
FYI, this is running on a 2010 2.66Ghz i7 Macbook Pro. OSX Lion 10.7.3.
BANG! Just went again… This time all I did was hit the play button to start the scene playing.
I’m now going to have to take things out one by one to see if I can pinpoint the issue…
First stop, uninstall ‘Enhanced Editor++’ extension (as I’ve heard it’s somewhat incompatible with 3.5). Also, (and it’s just a hunch and probably a very long shot!) is that it has a ‘Rememberer’ function, which could cause issues during scene play. Will see…
We have been seeing lockups as well, it seems after a few hours of working in Unity it will freeze up. Its a big issue for us when we build our asset bundles (over 1200 of them) it will build about 400 then freeze up. We are currently rolling back to 3.4
On my Mac Book Pro it is freezing so often that it is barely useable anymore. It always locks the entire OS, unless I limit the CPU usage of it’s process so I can kill it instead of hard restart the entire laptop. Good thing is that it haven’t caused any losses so far, unlike 3.4 - once it crashed in a way that erased my entire scene. I wish I never upgraded to 3.5, now I work 5 times slower because of the frequent restarts.
Bump! Any news on this? Bug reporting won’t be possible with an unresponsive OS, so we can only hope for somebody in UT to pay attention to the troubles their customers have while using what they paid for.
No, because it won’t mean anything to me if Unity doesn’t lock the OS only with empty projects. It seems a dead end to me - no reverting back to 3.4 is possible, no indication of activity on this issue, no way to work on my project at all.