I installed the unity web player on my imac with OS X 10.4, and when unity tries to load any game it completely crashes safari.
The loading bar gets to the very end and then crashes.
Any ideas? The machine is only a few months old.
If you run your game inside the Unity Editor, do you get any error messages in the console? If so, you need to make sure you are not getting those…
No, I am able to run the sample games in the editor without any errors. I can also run a compiled version of the sample game.
I recently reported a problem that’s not quite the same, but maybe it’s related - I see Unity crashing the browser (Safari and Firefox on Mac, haven’t tested on Windows) when executing WWW.LoadUnityWeb to load a new player (whether it’s a 1.x player or one that’s been rebuilt with 2.0). So my initial “menu” player on fugugames.com loads fine with Unity 2.0, but once I pick a game to play it’ll crash without saying much in the Console, except that it logged a Firefox crash.
Can you post a build for others to test to see if it’s just your machine or a greater problem? Even if you can’t share one publicly we (Unity Technologies) would love to test it privately and make sure that any potential bugs lurking about get resolved.
Crashing is bad, m’kay? 
Please use the Report Bug.app for reporting bugs.
If you are loading content from the gallery, make sure to provide the link and a stacktrace. If you are loading your own content, include a project folder and the built unity3d files and html.
Just a heads up for additional info on this problem, I got the same problem last night from a webplayer built with Unity 2.0 on 10.4 as well.
On both Safari on Mac and IE on PC, when I ran the game, the GUI was highly messed up (positions and layout all over the place), OnMouseDown events were not triggering, performance was low, then on exit the browsers crash.
I found out what was causing this. I had some very simple file access code using System.IO (FileInfo and Stream) and System.Xml.Serialization that was running in a Start(). I disabled the functionality of that loader for the webplayer, but I didn’t actually remove the loading call itself as I just figured Unity’s web security settings would either disable it, or at least throw an error. Since I was just prototyping anyway I didn’t think it would be a problem.
Commenting out the line that called my simple loading script instantly fixed the problem completely.
Like those above, it ran perfectly in editor, and in standalone.
I can’t send the project file, but that should provide some helpful info.
-Jeremy