Newest Unity often crashing?

Is it just me or is the newest version of Unity just crashing a lot? Might be my project but it seems rather random.

I crash when i try to start a scene that i just started 10 times without a problem...
I crash when i try to save my project that i just saved a lot of times without crashing...
I crash when i try to save a scene that i just saved a few times without a problems....
And i crash.....

And with crashes i mean it will freeze up, so i have to close it down from my task manager.

Think my Unity crashed like 20 times while working for 2 hours yesterday, which is rather annoying.
Got the same problem on my laptop after i updated to the newest version.

So does anyone else have a lot of crashes? Or maybe it is just my project

 

I've found Unity 4.5 crashes lots more then 4.3, but I'm not sure if thats just because I'm using it more or not.

 

Unity crashes at least 5 - 10 times per day for me.

I've gotten used to having to save my scene/project ANY time I change anything, since I've had way too many instances of me doing a lot of work, Unity crashing, and then having to redo it all again.

 

Same! problem is that it some times crashes when i try to save

 

Ditto BFGames, I crashed / stalled so much i reverted back to 4.3.x, as I cant afford the frustration nor the time lost due to the problems 4.5 caused me.

4.3 is solid.

 

This happens after using Debug.Log on a huge text file

 

@Graham Dunnett , It didn't crashed 4.3 (It logged as much as the Console allows). The current project I'm working on just migrate from 4.3.4 to 4.5.1. Not a massive inconvenience as there are ways working around it, as you suggested, but it just a surprise to me when I encountered it since it was working on the previous version

 

Last crash:

Reloading assemblies after finishing script compilation.
Begin MonoManager ReloadAssembly

Unity just freeze up forever

 

How can i do that when my program just freeze up and i do not get any of those informations?

 

Ohh where do i find the information then? Just looked through my editor log

 

As i said then Unity will freeze up so i in the end needs to close it down from task manager - so i never get there.

 

Seems to mainly happen now when it tries to compile scripts

 

Nope, but he said it would hoover up all things needed, but it never shows up. But i will send the project via the application now. But its huge so will take sometime.

 

I have the same issue! Here is the screen shot. The project works well on unity 4.3. Hope someone figure it out.

 

I have the same issue! Here is the screen shot. The project works well on unity 4.3. I think it's a huge bug of unity 4.5.1.

 

Solved. It's because I Debug.log() a long string. So damn speechless.

 

Thank your for the explaination.

 

Hi,

Not sure if this is the same problem that others are seeing (big debug log?) but I too am getting very frequent crashes since updating to Unity 4.5 (and now 4.5.1). I have reported a few bugs with whatever logs the crash reporter adds, but the one bug with the most info is 616919. If you have any info about it I'd be happy to hear it

 

Mine seems to take up CPU alot (Unity 4.5.1f3 lags when I try to do something on the scene but no crashes) but I don't know what the cause is and since my laptop is 5 years old I don't know if it is my laptop.

Unity 4.3 works really great for me even though my laptop specs are old but works. Currently reverting back to 4.3 until this is fixed. I thought I was the only one.

Edit: I created a new project on Unity and it seems to lag whenever I do something on the scene. It just an empty scene with nothing on it. and it happens too everytime I save the project.

 

We're seeing this on our team as well. I can reproduce it easily by opening our project, pressing Play, Stopping and pressing Play again. Unity just hangs and I have to kill it from the task manager.

This wasn't happening a few days ago and if I rollback our project to that time, it seems to work fine.

I'm using 4.5.1f3 and others on our team are still using 4.5.0.

 

Case-number by the way: 616104