We’re developing a shooter game and the client (of course) experiences frequent lock-ups in Safari. It seemed that some (but not all) were cause by the character reaching checkpoints that were either below the ground surface or interfering with other collision boxes. He’s using the latest Safari and he just updated the plug-in but no dice. Any ideas?
Let me see if can provide a little more context…
We are seeing lockups in both the web player, and also the editor during game play. Game play freezes, and the application (Safari or Unity) needs to be force quit. Nothing out of the ordinary appears in the Unity logs. We’re running entirely on Macs here.
We’ve noticed that these lockups seem to happen in places where collision boxes are intersecting, such as the bounding box around a car being partially underground or, most often, the trigger box for a checkpoint intersecting with other collision volumes. As we’ve removed these intersections, the frequency of the lockups has dropped dramatically. But we haven’t been able to stop them entirely, yet, and we are getting very close to launch now.
The issue may be related to the size of our project, as I haven’t been able to reproduce it in smaller test levels.
Has anyone seen anything like this before? Any suggestions on how to diagnose the problem when one of these lockups occurs?
Thanks!
Actually, my game experiences this on Mac too. Completely ruined the tests we were running 
Have you tried with other browser or standalone? Because everything froze on Mac for us. Seemed to crash when entering a collider…
Have you tried on PC?
There wasn’t until recently an official version of PhysX for osX. As such, the osX player uses a custom version of PhysX hand ported by Unity themselves.
Submit an official bug report, it sounds like you might have found one.
I opened bug #402150.
After more testing, we’ve confirmed that these lockups only happen under Safari and Chrome on Mac OS X. Firefox on OS X works fine, as do all of the browsers under Windows. So it looks to be a problem with the Unity Web Player under WebKit on OS X.
In case anyone stumbles across this thread: we narrowed the problem down. We had AudioSource components on each of the player model’s feet, to play footstep sounds. If we get rid of those, and play the footsteps through an AudioSource at the root of the skeleton, the problem goes away. Alternatively, we can also remove the Rigidbody from the root of the skeleton, and everything works fine. So it seems to be related to having (3D) AudioSources in an animated hierarchy underneath a Rigidbody component. Bug is still open, but hopefully we’ve narrowed it down enough for the Unity folks to solve it.