MacOS Builds Crash - Unity 5?

[stevej]

I'm having some problems since upgrading to Unity 5 (and updating to the latest NGUI as of about 2 weeks ago) where my Mac builds crash while running. If I create a Development Build, or I run in the Editor, then I don't see any errors at all.

I've got a thread for this on the Unity forum, so I'll copy and paste a bit of that in here.
http://forum.unity3d.com/threads/mac-os-builds-crashing-in-unity-5.316489/#post-2066544

In particular:

What's interesting is that it seems to happen in the same spot in each scene where it happens. e.g. my "MainMenu" scene loads up fine and has no issues running. If I go into my "Credits" scene, it freezes almost immediately. If instead, I go into my "PartyBuilder" scene (I'm building an RPG), then it doesn't freeze until I try to click a button.

The common element is NGUI. Maybe there is something going to there.

Any thoughts? Anyone else able to try a Mac build with a few scenes and see if they run into any problems?

[ArenMook]

Unfortunately there isn't much I can do here. Note how using an invisible OnGUI "fixed" the issue for another poster? That's called a hack -- and a clear sign that Unity broke something on their end.

OSX builds have other similar glitches. For example when running a game with Steam overlay enabled on OSX, if NGUI is used the entire screen will turn green on startup half the time. Adding an invisible OnGUI element or a 3D cube to the scene works around the glitch for some.

Your best bet would be to create a repro case and submit a bug report to Unity, as anything that works on one platform and causes Unity itself to stop responding on another platform is a regression bug on their end.

[Samuraisa]

Sorry for necroposting, I just want to add:
I spend almost a week to find out why our project craches on linux and macOS after migration from U4 to U5. It's crashes has many mutually exclusive moments (the same actions on different objects in one place works in other crash) so I don't blame NGUI till today. Tonight I've found (localize) the source of the problem by creating fully new clear project with only NGUI imported.
I've made a scene with 2 sprite-buttons switching states of gameObjects of each other (click on first shows second and hides first itself with UIToggle+UIToggleObjects and vice versa), tested it and everything runs smoothly. But I had only to add any UILabel on the scene and it crashes. Further investigations shows what crash occurs only on disabling gameObject with UILable on the scene.
Maybe it helps to report this problem to Unity devs.

I can send you my test scenes if u need them.

P.S. And yes - hack with OnGUI () works for me.

[ArenMook]

Unity 5.2 + dynamic fonts = crashes on save. Unity 5.2.1p2 fixes it as I understand it. I've also posted a suggestion to fix it without updating Unity here: http://www.tasharen.com/forum/index.php?topic=13627.msg61039#msg61039

See this thread for more info:
http://www.tasharen.com/forum/index.php?topic=13588.msg61062#msg61062

[Samuraisa]

No any crashes on save. Crashes in runtime when any UILabel present in scene and any gameObject.SetActive(false) (not necessary UILabel gameObject, just "any").
Linux and OSX builds only, Win32 + Win64 are OK, also I work in Win Editor, so don't know about mac editor issues if there are any.

To many "any" in the post spotted

---------------------------------------------------------------------------
Edit:
Also no dynamic fonts, using one of the NGUI demos atlas-based fonts for tests (Arimo20).

[ArenMook]

Sounds like something you should report to Unity to fix. In general any crash = Unity issue to fix, especially if it works on one platform but is broken on another.