Unity 4.5 crashing every single time

Hey all, I've already submitted a bug report for this, but wanted to post it here as well. I just upgraded to 4.5 and I can no longer play my project in the Editor. Unity will immediately crash without any warnings or errors. 4.3 was just fine. My specs:

Mid-2010 Macbook Pro
OSX 10.9.3
2.4 GHz Intel Core i5
8 GB RAM

Anyone else having issues? Thanks.

EDIT: These are the last lines I'm seeing in the Editor.log file

EDIT 2: I actually cannot run ANY project in Play mode in the editor, even a blank new one..

 

Out of curiosity do standalone builds work?

 

Case 610044, but it never actually launches the bug reporter so I had to manually open it up and submit it - I'm assuming the crash logs weren't sent?

 

Just for clarity, you say you cannot "run" any project, do you mean like, hit-the-play-button-and-it-crashes, or opens-the-project-and-it-crashes?

 

I mean hit-the-play-button. The projects open up fine, and I can create a new project fine, import assets, etc. As soon as I press Play the entire app crashes (and then I get the standard OS X "Unity crashed unexpectedly" error).

 

I am able to build and deploy to iOS without issues. Seems to be an in-editor Play mode thing only (which is still debilitating of course).

 

Same here! 4.5 crashes even when I play a new empty scene in a new project. I've rebooted, wiped, reinstalled... it's no good. Have to roll back.

 

Phew, glad I'm not alone. I'm rolling back now too (which sucks because I really need the new features!).

By the way, what are your system specs?

 

I found my issue. I was outputting a string to the debug.log which was too large for the editor to handle. It worked fine in 4.3. The string was about 25,000 characters and the callstack was


count <= std::numeric_limits<UInt16>::max()
UnityEngine.GUIStyle:INTERNAL_CALL_Internal_Draw2(IntPtr, Rect, GUIContent, Int32, Boolean)
UnityEngine.GUIStyle:Internal_Draw2(IntPtr, Rect, GUIContent, Int32, Boolean) (at C:\BuildAgent\work\aeedb04a1292f85a\artifacts\EditorGenerated\GUIStyleBindings.cs:724)
UnityEngine.GUIStyleraw(Rect, GUIContent, Int32, Boolean) (at C:\BuildAgent\work\aeedb04a1292f85a\artifacts\EditorGenerated\GUIStyleBindings.cs:717)
UnityEditor.ConsoleWindow:OnGUI() (at C:\BuildAgent\work\aeedb04a1292f85a\Editor\Mono\ConsoleWindow.cs:423)
System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception)
System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222)
System.Reflection.MethodBase:Invoke(Object, Object[]) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Reflection/MethodBase.cs:115)
UnityEditor.HostView:Invoke(String, Object) (at C:\BuildAgent\work\aeedb04a1292f85a\Editor\Mono\GUI\DockArea.cs:241)
UnityEditor.HostView:Invoke(String) (at C:\BuildAgent\work\aeedb04a1292f85a\Editor\Mono\GUI\DockArea.cs:234)
UnityEditor.DockArea:OnGUI() (at C:\BuildAgent\work\aeedb04a1292f85a\Editor\Mono\GUI\DockArea.cs:671)

[C:/BuildAgent/work/aeedb04a1292f85a/Runtime/Filters/Mesh/LodMesh.cpp line 287]
(Filename: C:/BuildAgent/work/aeedb04a1292f85a/artifacts/EditorGenerated/GUIStyleBindings.cs Line: 724)

maxVertices < 65536 maxIndices < 65536*3

(Filename: C:/BuildAgent/work/aeedb04a1292f85a/Runtime/GfxDevice/d3d/D3D9VBO.cpp Line: 638)

 

Unity is also crashing (and showing me the bug reporter) pretty much every time I hit "Play"

I'm running a Macbook Air (Late 2010)

 

Additional issues for team:

fmod bugs
http://forum.unity3d.com/threads/248335-Unity-4-5-FMOD-errors

false positive virus
http://forum.unity3d.com/threads/248291-Unity-4-5-mono-exe-virus-detected-problem


Fear not folks! Sustained Engineering team has your back!

 

http://forum.unity3d.com/threads/248321-4-5-Serialization-Depth is a crash too now...

 

installed 4.5
crashing on every scene we have....even super simple test scenes.
unity starts up but when we push play it hangs and the bug reporting UI pops up. even after submitting the bug, unity never recovers and sits there spinnning untit force quit

running a
macbook pro retina early 2013
3ghz core i7
8gm 1600mhz ddr3
osx 10.9.3

 

Getting this problem as well. Mac/Linux/PC builds all run fine, just can't run in editor, with no helpful error messages.

A reboot seemed to have solved it... for now?

 

On an old MacBook Pro running OS X 10.9.3- after upgrading to 4.5, I can no longer open the scene I was working on or it will crash. Every time. I can open the project and an empty scene, but if I try to load my main game scene, it will crash (trying to import assets, spinning rainbow cursor, using 195% CPU, fans spinning up, "not responding" for a minute or so, then "Unity unexpectedly quit".)

Not good. Restarting didn't help, so I'm downgrading to an old version I had on another partition and waiting for a less buggy 4.5.x release.

 

upgraded to 4.5 Mac OSX 10.8.5. Crash every time I hit play across a variety of projects - requires force quit to exit. No helpful information, no bug reporter. Just a voice in the back of my head saying "I told you not to update something always goes wrong with Unity these days."
I guess I got hopeful when they said 450 bug fixes. Looks like a big waste of time to me.

 

They have opened the editor 73224 times but, have they pressed play also...?

 

Yea - the first one had tons of serialization depth errors from one of the 3rd party assets I purchased, and I assumed that was the problem. Unfortunately, it has nothing to do with it as even when I create a shiny new empty project, Unity still crashes with nothing but that lone NULL ref exception.

 

Is it possible to become a beta tester? I seem to have major, major show-stopping bugs every single new release - I've never had a new release just work. I don't know what's so special about my specs/environment, but maybe it would be useful.

 

Case 610039

New project created in 4.5, new empty scene... Crash on play.

OSX 10.8.5, Late 2012 Macbook Pro 2.5 Ghz, Intel Core i5, 4GB RAM, 1600 Mhz DDR3

 

Thanks for this. I was having the same issue and found a place where there was a debug log of a large text response from our webserver and it was causing this same crash. It used to just crop the response.

 

no update on this??
our issue number is 610120

it works on some of our development machines but not for lead programmer who reported the bug.

update: turns out it was my bluetooth logitech trackpad that was causing it. i turned it off and it's working now. this is a workable solution for us for now but still hope it gets fixed eventually.

 

i cant load my project without a crash, i can create a new project but crash on play, lol its ironic that this build killed 450 bugs, yet theres new major bugs going around

edit:
updating broke my library folder(the metadata etc) and i couldnt run my project in 4.3.4 anymore, but i deleted this folder and reopened unity 4.3.4 and it recreated the folder without issue, i have yet to try this on 4.5 but i wont until a new unity update lol

 

I was able to consistently reproduce this issue and consistently fix it. I'm not totally sure what did it, but here are the details...

I'm using Unity 4.5.0f6 on a late 2012 Retina MacBook Pro. When I have a PlayStation 4 controller plugged in via USB, Unity will crash any time I hit the play button (even on a brand new project). If I unplug the PS4 controller and then hit the play button again, everything works fine.

I don't have any other controllers to try this with, but it sounds like there's something wrong with the way Unity is handling peripherals.

 

And I've always had a PS3 controller plugged in...

Will report back, re-installing 4.5...

Nope, didn't work for me :/ Crashes no matter what.

 

Same Here!
Tested in Mountain Lion and Mavericks...

 

Try restarting the machine without any peripherals plugged in. I restarted and it seemed to help a bit. It might also be an issue with USB and other peripherals, and not just gamepads. I'm only guessing here though!

 

Confirmed on my end that restarting with no peripherals seems to keep everything sane on my OSX copy of Unity. Crash with PS3 or PS4 controller plugged in (probably xbox too? haven't tested yet)

 

Same here, I only get this crash with my PS3 controller connected. Works fine otherwise, late 2010 MacBook Pro running mavericks.

 

I haven't restarted - will try one morrreee time.

 

VERIFIED over here as well! It's definitely my PS3 controller - except I took it a step further. I don't think it's the USB connection to the controller, but the Bluetooth. If I disconnect the PS3 as a bluetooth device then it Plays fine in editor. If I activate the controller and have it connected via Bluetooth, it crashes every single time. Disconnect and it runs fine every single time. No need to restart.

Can you guys verify if it's Bluetooth and not the USB?

Thanks a TON nickpettit, I can at least test my game with keyboard controls for now.

 

Unfortunately, I don't have a USB controller but it crashes only when I have the PS3 controller connected to my laptop via bluetooth regardless if the USB cable is plugged in or not (I still hook up the controller to my laptop via USB to keep it charged).

 

I can hit play, but if I click anything on the Project tab it's a instant crash. Which means I cant even open scenes. Which means the engine is useless now.
Re-installed 4.3 and now the problem persists, so this is project files corruption.

 

Confirmed that unplugging my PS4 controller and rebooting changed things back to normal.

Before: pressing the play button would hang Unity every time. (OSX 10.9)

 

Had the PS4 controller connected via USB and Unity 4.5 would crash every time I pressed play on any project. Disconnected the controller and everything works fine. Using OSX 10.9

 

Cases 610746 and 610748, but I've been able to reproduce it with an empty scene and no assets.

 

Also had the PS3 pad crashing 4.5 on my Mac. Connected by Bluetooth, it was working fine until 4.5, now the Editor just hangs on pressing Play.
Took a while to narrow it down but the Pad, when connected by Bluetooth is the definite cause, plays fine with Bluetooth OFF. Not good as my game is multiplayer and requires a couple of pads.

** Good thing is I dropped back to 4.3.4 and my project runs perfectly **

(Running Snow Leopard OSX btw)

 

Good catch!!

I was working on my laptop from the office with no problems, then came home and suddenly hitting Play causes Unity to hang with this error:

Code (CSharp):

1. Receiving unhandled NULL exception
2. Launching bug reporter
3. Receiving unhandled NULL exception
4. Launching bug reporter

The difference: at home I had a Playstation 4 controller plugged in! Unplugging my Playstation 4 controller fixes the problem immediately.

 

Awesome news to hear. Looking forward to this being fixed!

 

Great, thanks!