Unity 5.2 crash when Application.LoadLevel is called at Start (with UI in the first scene)

Hi,

My project is instantly crash when I launch it. My object aren't sorted by Alphabetical order (so it's not the DontDestroyOnLoad issue).

Here is my crash log. Anyone experienced crash issue ? Two project of our team can't run Unity 5.2 without a crash in a minute in the editor, or instant crash by pressing play.

We are pretty disappointed here as all unity upgrades since 5.0 never doing bad stuff like this in the past.

EDIT 1 : More information, we figure out that we crash when we are changing scene. I'm still investigate.
EDIT 2 : We found the issue : if Application.LoadLevel is called in Start(), the editor crash. I'm looking for a test project for issue tracker

EDIT 3 : We reproduce it :
1) Make two scenes
2) Import some images, set in Sprite mode
3) Right click on scene -> UI -> Image, it wille create a simple canvas with an image inside
4) Put one of the image imported on the Image component
5) Make a script that do Application.LoadLevel("Scene2") on Start
6) Run -> profit the crash.

 

Thanks, I posted an issue into the issue tracker just after I edit my post here with my example project.

 

thank you for showing this up, I have exactly the same problem and I was scared that it is related with my Smartfox implementation :O

I will go for a workarround with calling the ApplicationLoad over a different method after switching a flag in the start method.

 

You can just call a coroutine and call your level after a "yield return 0", it will skip the first frame and do the trick !

 

hmm

i am not that familar with Coroutines. i tryed this, but my Unity still Crashs :/

i wrote this and i am calling it on Start() with StartWorkaround();

Code (CSharp):

1.     IEnumerator Workaround() {
2.         yield return 0;
3.     }
4.  
5.     IEnumerator StartWorkaround() {
6.         yield return StartCoroutine("Workaround");
7.     }

what exactly is wrong here?

PS.: For now i was able to solve my problem by changing the method from Start to Awake, not a nice workaround but it works.

Kind regards
Tepoo

 

Well... Almost everything. =)

You should do something like this:

Code (csharp):

1. void Start()
2. {
3.     StartCoroutine("LoadMyLevel");
4. }
5.  
6. IEnumerator LoadMyLevel()
7. {
8.     yeild return null;
9.     Application.LoadLevel("MyLevel");
10. }

 

Oh, thank you. Documentation seems to be missing this info, never read that.

 

Wow, im learning new things day after day even after 3 years of Unity dev

 

thanks for this information

currently i am lucky that i don't need coroutines yet, but if the day comes, i know something more then yesterday

you guys are doing a good job
Keep up the great work.

 

I noticed that you can also simply replace Application.LoadLevel ("yourscene") in Start() with Application.LoadLevelAsync ("yourscene"). That stopped the crashes for me.

-act

 

Just tried that but unity just freezes instead of crashing to desktop :/

 

Taking a look, we seem to have a fix somewhere but it's not clear what change to fix it.

 

oh i see... you guys will figure it out I'm sure.

 

Same with crash here after upgrading to 5.2.1f1 from 5.1.something, i enabled a game object that was responsible for changing scenes and editor crashes.
Compiled version does not crash but compiling doesn't help testing.
Whatever you changed in the last update most probably broke it.
Application.LoadLevel crashes if it's called at Start or Update BUT it WORKS if it's called on Awake.
LoadLevelAsync works EVERYWHERE. This is not a solution however

 

This problem also persists with the latest patch release 5.2.1p2 . I also still have to use async load at the moment to not crash the editor. @phil-Unity, could you kindly recheck on your statement that there is a fix somewhere and the state of its integration in a future release? Thanks!

-act

 

Well, lucky for me that I use async for an animated loading screen then. I also still have 5.2.0f3

 

Any news on that? I also have a similar problem. It might not be exactly the same issue, but my linux headless builds crash with exactly the same setup (canvas+image+loadlevel). But in the editor (osx) it doesn't happen, maybe it's a slightly different thing..?

Reported it as case 734921 (5.2p3).

There's another thread here about the issue.
http://forum.unity3d.com/threads/5-2-sporadic-sigsegv-crash-in-linux-headless-builds.354031/

 

The problem still exists. I have this problem if there is Canvas in the scene. If I remove or disable the canvas, everything works fine

 

Have you tried using the current version (5.2.2) of Unity?

 

Actually, one thing I forgot to mention a while ago; I did find that if I had more than one UI canvas in a scene, the scene would freeze up after a random amount of seconds, forcing me to close it. Could be related? (I haven't tried again yet either...)

 

Yes. The issue presents in the last version

 

Being that I use LoadLevelAsync, I am going to have to see if I'm affected by this bug...

 

Fyi, todays release of Unity 5.2.3 seems to have fixed the problem for me.

-act

 

Which platforms? Also, good to hear that problem seems to be fixed.

 

This was a problem with the Editor only (OSX in my case). It's not related to running code on build targets.

-act

 

Ok then.

 

Hi all!

Ran into a similar (or the same) issue over here using the 5.3.1 editor and calling Appliation.LoadLevel...
Not sure if it's UI (I use NGUI) related or not.
But I used LoadLevel in Awake and the Editor crashed.
Now I changed this...
using UnityEngine.SceneManagement;
and then
SceneManager.LoadScene("MyScene")
This fixed the issue (since Application.LoadLevel is becoming obsolete).
Hope this information helps someone...

Diederik / Xform

EDIT: The problem came back strangely enough, so I'm guessing it's the issue that you cannot call this in Awake anymore. So I guess this issue is not fixed yet.

 

see
http://forum.unity3d.com/threads/5-3-crash-when-application-loadlevel-is-called-on-awake.373607/