Unity 3.4 Editor less stable?

Has anyone else noticed that Unity 3.4 is much less stable, at least on Windows? I’ve had previous versions run for literally weeks without a single problem, but in the last two days I’ve had 1 lockup, 1 crash with dialog, and 2 crashes without dialog (except to ask if I wanted to launch MS Dev 2008 to debug it).

Lucky you. 3.3 and 3.4 crash all the time on Windows7 64-bit, for me and others.

I’ve found a simple way to make Unity not crash (well at least limit the crashing).
As others have said, I agree it definately has something to do with making changes in the editor when switching back from Visual Studio or MonoDevelop, and then changing something in the Inspector or elsewhere.

Right now I’ve gotten into the habit of clicking on the window title bar of unity each time I go back into it. This small delay is usually enough to let your scripts compile. Then I go and make any changes in the editor.

Stupid sounding idea I know, but I used Unity for about 12 hours yesterday and it only crashed twice.

So when switching back, single click the Unity window title bar, and then go and do your edits. Works for me :slight_smile:

My experience with Unity 3.4 on Windows 7 (64-bit) is that the upgrade to 3.4 has made my projects crash the editor MUCH more often.

As far as I can recall, all my crashes has been somehow related to me updating/renaming/previewing c# scripts.

I think its the MonoDeveloper background compiler that crashes Unity editor, because if I stick to prefabs and hierachy editing, nothing crashes. Editing textures in a shader hasnt made mine crash yet either.

But as soon as I run a project and get eg. “NullExceptions” because I’ve forgotten to load some ressources and this happens 60/second. Eventhough I instantly pause/break my program when Console shows me the errors, sometimes it takes a few minutes and then Unity starts to go slow or become unresponsive and suddently we have the almight “hangman”…

I dont know if its related to having the player running in the Editor while I go to MonoDeveloper and start to fix the script for minor tweaks, but I often forget to pause/stop the Editor/player before I go back to MonoDeveloper and edit.

This COULD PERHAPS have something to do with ressources not getting properly destroyed/garbage collected by the Mono compiler. I really dont know and I seriously hope that the Unity developers themselfs are onto why this happens, because we have been looking at investing in the PRO licenses for our games very soon, but if Unity keeps getting worse, we might have to look for another platform.

I’m having the same problem in one day 3 lockups(needed power button of the computer).
And very slow respons.

In my case it seems to be because i’m using a dll plugin.

I started noticing the crashing today when I started scripting in 3.4 and make alot of changes within a short time. It most of the time happens whenver I wrote a line and hit that play button to check it out quickly. I also noticed that not always things update in the Inspector. I think it’s probably some sort of Refreshing issue of the Inspector so when you move too fast for Unity before it’s finished refreshing, it just outright crashes. Not that I’m the expert on this , just saying what it looks like to me since I observed it in that chain of events :slight_smile:

Unity 3.4, at least on 64bit Windows 7, is insanely less stable. Editor crashes used to be relatively uncommon for me, now my editor crashes every 30 minutes or so. Nearly all of the crashes are just while recompiling scripts (not hitting the play button or anything).