Unity 5.2 crashes a lot

...

 

This is happening to me too.

 

I was about to create a topic in regards to this issue, I get crashes all the time, specially when doing builds with a custom scripted menu (its just basically a shortcut to different build platforms, using BuildPipeline) and it's getting really annoying.

 

Thank Karl, seems that mine was actually caused by some recent changes to my own code. 5.2 has been stable for me since I fixed it!

 

It crashed a lot in my Windows 10 64bit PC too. Every 5 min or so. Now I downgraded to 5.1.3 and it works ok.

 

I always submit reports when the report window shows up. https://fogbugz.unity3d.com/default.asp?726438_8poi1l1sv6uukgtq

There you go.

 

Since 5.2, I have been experiencing lots of crashes too. Mostly when trying to build a game, but also in editor too. Unity has been extremely stable for me, until now.

I'm using windows 8.1 64-bit.

EDIT: ....aaand the editor just crashed again. So far it has happened when entering to play mode or opening a scene. No crash reporter window with these.

Faulting application name: Unity.exe, version: 5.2.0.38013, time stamp: 0x55e09432
Faulting module name: Unity.exe, version: 5.2.0.38013, time stamp: 0x55e09432
Exception code: 0xc0000005
Fault offset: 0x0000000001492fae
Faulting process id: 0x2cc
Faulting application start time: 0x01d0eee86d342d99
Faulting application path: G:\Games\Unity\Editor\Unity.exe
Faulting module path: G:\Games\Unity\Editor\Unity.exe
Report Id: 8fada068-5aef-11e5-8304-e03f4946fbe7
Faulting package full name:
Faulting package-relative application ID:

 

5.2 has a known issue with the alpha numeric sorting method for the hierarchy window. Make sure that you're disabling this feature.
See: http://forum.unity3d.com/threads/un...ing-play-mode-every-time.350171/#post-2290495

Additionally, when posting about an editor crash, you can better help yourself and your peers help you with your issue by attaching a copy of your editor log located in "C:\Users\USER\AppData\Local\Unity\Editor"

Using a text editor find the phrase "crash", unfortunately the exception report you posted Polkatuba is not helpful.

This is always preferred because Unity reps and employees can not respond to every crash post.

Usually the editor will call a script before the following fault in the application. You can almost always debug an issue yourself using this method as the crash will almost always be a fault in your project files.

 

For me, the alpha numeric sorting was already disabled. But I'll be trying to send the log files with the built-in bug reporter next time it happens.

I have been able to work with this project for months without a single crash. Then after updating to version 5.2, the crashing started to happen. It could be something in the project too but nevertheless it's not what you should expect after a software update.

 

If on Windows: I would also make sure you have installed and updated Visual C++ redist files for all versions: 2005, 2008, 2010, 2012, 2013 and the 2015 version. Afterwards download the full distribution of directX and install. Afterwards use the directX web updater and then install the latest drivers for your graphics card. Afterwards run windows update, to get the service packs for all C++ redists.

Not a guaranteed fix, but has fixed empty project crashes for me in the past. Also, for some reason... update your system clock to internet time.. I know.. but it has worked for me in the past.

It's easy to believe that it's the editors fault but most times its an external tool or outdated calls in your logic.
Good luck and Ill keep watching this post and offer whatever help I can.

 

With troubleshooting I've narrowed the issue to the animator, and more specifically the animation override functionality. I've also file a bug report, and it's showing as resolved in the upcoming patch. I tried creating a work around script this morning, but it's triggering before I can access it externally. So for now, no animator component on objects allows for development.

 

Why doesn't support reply to my emails? I have even threatened to file a complaint with BBB. I have an issue that I sort of resolved but this was after waiting over a week to hear back from them. If they're really that busy they could at least take a few seconds to say so.

 

I can see your support email hasn't been replied to in over a week. I'll prod the support guys. It's strange that it's not been resolved for you.

 

Rotating the scene view, ( Alt+LeftClick ) crashes a lot!! Anybody else?

 

Haha, I thought it was just me before I checked the forums. I'm using Unity 5.2 on Mac version 10.11 (El Capitan public release version). It's been the same story for me with Unity crashing all the time unexpectedly.

Hopefully the guys at Unity can work their magic and make a stable release soon. Either way, I'm just glad to know I'm not the only one.

 

Yes. They finally got back to me and said they say there was absentees with some staff.

 

It crashes for me as well, 32-bit Windows 10. However, I am running Unity under CDB like this:
P:\DEVELOPMENT\Unity5\Editor\Unity.exe -force-opengl -silent-crashes -projectPath P:\CPP\Crafterria\trunk\unity-client

So I cannot catch the reason of the most crashes, however I am having the log all the time displayed into console.
While in 5.0, crashes were due to my native plugin and I know about them, in 5.2 I get crashes in very strange places, like, in mono while processing a breakpoint.

Due to --silent-crashes flag, I cannot send bug reports with ease, because the popup is extremely annoying when I develop the native plugin itself (in this case crashes are welcome, it's C++ after all)

But I will dump logs here on next crashes

 

I'd like to report that I've been experiencing frequent crashes as well, both in Editor and in build, with our upgrade to Unity 5.2.1f1. This crash is occurring without Unity popping up the bug reporter, and I've attached the editor log from the most recent crash. What I find most interesting is that the editor log has no Stack trace associated with the crash. Still, hopefully this information helps. We had to go to Unity 5.2.1f1 to fix some of the weird lighting/shadow issues we were experiencing in VR. That issue has been fixed, but this new instability has us concerned.

I will also submit dump logs here next time I get a crash, if I can.

Here are also my Window's Application Log Event for the crash.

Faulting application name: Unity.exe, version: 5.2.1.29534, time stamp: 0x56002fd9
Faulting module name: ntdll.dll, version: 6.3.9600.17736, time stamp: 0x550f4336
Exception code: 0xc0000005
Fault offset: 0x000000000003b179
Faulting process id: 0xf64
Faulting application start time: 0x01d106af68722ff1
Faulting application path: C:\Program Files\Unity\Editor\Unity.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5fde7a8e-72a7-11e5-82fd-3417ebb28c6c
Faulting package full name:
Faulting package-relative application ID:

 

Had another crash just now when trying to trigger a build. Couldn't capture the crash dump, sorry.

~~~
Faulting application name: Unity.exe, version: 5.2.1.53642, time stamp: 0x5615973c
Faulting module name: ntdll.dll, version: 6.3.9600.17736, time stamp: 0x550f4336
Exception code: 0xc0000005
Fault offset: 0x000000000003b179
Faulting process id: 0x794
Faulting application start time: 0x01d106baf412f136
Faulting application path: C:\Program Files\Unity\Editor\Unity.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c7d39df5-72b9-11e5-82fd-3417ebb28c6c
Faulting package full name:
Faulting package-relative application ID:

 

Yes, same to my case. It happens so many times (like 90%) while play testing. Attached the log after I clicked the "pause" button of Editor. Hope this helps.



Crashed Thread: 2



Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY



Application Specific Information:

abort() called

*** error for object 0x12ae8af00: pointer being freed was not allocated

 

I installed latest patch release in hope that it would fix the crashes for me but it did not It crashes 90% of the time when I exit play mode and when I try to build. The starnge thing is why does it work in the remaining 10% if I don't change anything?

 

I submitted it a crash report after one of the crashes. Actually I haven't tried it with empty project. But for now I wont be able to do it because I reverted to 5.1.4 to be able to continue to work.
But the strangest thing is that 1 out of 10 times I could do a build without a crash.

 

I just upgraded to 5.2.2 on Mac El Capitan and my project unexpectedly crashes at the same point over and over.
I have no infinite loops so I am not sure what is happening.
For now I will just degrade to 5.2.1.

Anyone else suffering from the same issue?
Thanks.

 

Me too, with Unity 5.1 all work fine, but with 5.2 crash all time with same projects, is really bad.

 

unity 5.2.2 crashes non stop for me. Also i use Playmaker, and when I press restart level (You know sometimes you want to restart the level to test things over and over) the main light source does not come back! But Again it crashes non stop if you have a scene with a decent amount of polys but nothing major...

 

Same crashes for me and reported the bug. The logs seem to show something to do with terriain as my issue which is odd because there is no terrain in my scene:


0x00000001407A2001 (Unity) `anonymous namespace'::SynchronizeTerrain
0x00000001407B6708 (Unity) AssetInterface::StopAssetEditing
0x00000001407B7626 (Unity) AssetInterface::ImportAssets
0x00000001407B7A76 (Unity) AssetInterface::WriteRevertAssets
0x0000000140C814D7 (Unity) Application::SaveScene
0x0000000140C83400 (Unity) Application::FileMenuSave

However one thing to note is this happens every time I try and save the project making 5.2 (even the latest patch 5.2.2p) completely unusable for me

 

@XCO make sure you have the latest version of playmaker. Unity keep crashing for me when using playmaker until I updated to the latest version.

 

Getting a lot of editor crashes since updating to 5.2.x - here is the latest crash stacktrace from 5.2.2f

========== OUTPUTING STACK TRACE ==================

0x0000000140289AE2 (Unity) BuildScriptClassId
0x00000001402909D5 (Unity) FindOrCreateMonoScriptCache
0x0000000140282896 (Unity) MonoBehaviour::SetupScriptingCache
0x00000001402853FC (Unity) MonoBehaviour::RebuildMonoInstance
0x000000014045B2FB (Unity) MonoManager::RemoveBehavioursFromManager
0x000000014045CB26 (Unity) MonoManager::EndReloadAssembly
0x000000014045E75D (Unity) MonoManager::ReloadAssembly
0x000000014079610A (Unity) ReloadAllUsedAssemblies
0x0000000140C77A66 (Unity) Application::LoadSceneInternal
0x0000000140C79E95 (Unity) Application::EnterPlayMode
0x0000000140C7A77A (Unity) Application::SetIsPlaying
0x0000000140C80C19 (Unity) Application::TickTimer
0x0000000140E3D6C4 (Unity) RelaunchUnity
0x0000000140E3EC7B (Unity) WinMain
0x000000014153A760 (Unity) strerror_s
0x00007FFB90642D92 (KERNEL32) BaseThreadInitThunk
0x00007FFB92D49F64 (ntdll) RtlUserThreadStart

========== END OF STACKTRACE ===========

 

Crashing for me as well...
I have a HP Zbook Windows 7 64-bit , and I'm getting the "old" windows friend again - Blue Screen of Death.
What I did?
I just installed the Unity 5.2.2f1, and selected run after install.
Unity 5.1 is running fine.

 

In 5.2.2 my project crash every time when i save my project before that i am using 5.0 thats work fine for me

i am using mac book pro

 

Editor 5.2.2f1, p2 and p3 crashes each time on exit, losing settings and re importing all files on startup.
case # 743925

 

unity 5.1 crash a lot ....... too

 

Hey guys, after update the Unity to 5.2.2 I've got the exactly same issue of bojan1986819. 90% of the time after close the game mode my Unity have a crash... I made some tests trying to fix the problem, but seems something of the new version. Here some things I realised in my project:

• If I don't change anything in my scene, the crash doesn't happen.
• The crash doesn't happen in new empty scenes.
• Not all changes in my scene made the Unity crash, it seems something related with the cameras. Because if I change some post effect or move one of my cameras it is 100% chances the Unity will crash after stop the game mode.
• I deleted all cameras from my scene and the crash stop happen.
• Update the Unity to 5.2.2 bring me this error too:
  Screen position out of view frustum (mouse pos 256.000000, 0.000000, 1000.000000) (Camera rect 0 0 256 256) I'm not sure if is related...

For now I just downgrade my Unity to 5.1.4 and everything is working fine.

 

Watch where the GI cache is written on disk, changing its location has solved most crashes.

 

Has anyone tested to see if version 5.2.3 solves these crash issues?
I tried to use version 5.2 when it was first released but it was crashing so much I had to rollback to 5.1.

 

I try it, but still is crashes.

I have found strange crash does not occur in of the PC version.

NO~~~~~~~~

 

new bad news ....... crash on windows 8.1 (unity 5.1) and crash too on a mac maverics OS (unity 5.1)

 

I've been getting a ton of crashes as I enter play mode in the editor. I've sent in some automated crash reports, though I've had to remove the project (no time for many gigs of uploads). The stack trace is just a long list of dll's, though.

Most of the time, though, the editor crashes without opening the bug reporter. There's also no indication of there having been a crash in the editor.log. Only a windows standard "The program has stopped working" dialogue.

I've mostly been able to avoid this by going into playmode in a lightweight or empty scene first, and then using Unity as normal. Other than that, there's no consistency - it can happen on any scene. We're not using any lightmaps, and baking is off on every scene, so I doubt it's the GI.

 

I submitted a bug that crashes Unity every time, but haven't received other than an auto response, and don't see it in their database of bugs. So - in case this helps anyone, executing this single line of code will cause Unity to crash:

Code (csharp):

1.  
2.   if (RectTransformUtility.RectangleContainsScreenPoint(null, Vector2.zero, null))
3.         throw new UnityException("it will crash before it gets here");
4.  

 

Is that the same as case number? 744674

Maybe I'm just not searching right. Is there a way to see a searchable list of bugs, where I can put in the case number and pull it up?

 

So there's no way to search the issue database by incident number then? Or is it an option only Pro users see? Because I don't see my bug on that page link you gave, and I see no way to find it either.

I also see this big red text I see when I go there - "You need to sign in or sign up before continuing." It shows that even though I'm already signed in.

 

Same here, started to happen in 5.2.2. And i know what triggers the crash: preview window..

If you have prefab selected and it's preview is visible under preview window and you click "play", it crashes. On one project (it's trash project so i didn't think twice when it started crashing, it's the one where i deliberately mess things up..) it crashes when i have even material thumbnail visible in inspector in that project.. Camera preview, same.

Everything with a preview is prone to crash in 5.2.2. I was sure it was my own trashproject and it's multiple bad practices and no cleaning but now it happened on brand new project with no tools or assets imported: had prefab preview open, crash, then on next launch drag&drop didn't work (same with the trash project, opening the scene where the crash happened, cause multiple bugs, no drag&drop to scene or to hierarchy, instead an error (sorry, was in "get this project back up asap" mode so didn't catch it.) On next launch it worked again.

Also, no editor.log and no crash report dialog. The symptom is so odd that it took long time to find out what it was. Reverting back to earlier version until this is fixed. Build work 100%, it's only in editor.