- Home /
crash in standalone but not in editor - appears to be caused by UI
I have a project that runs without errors in the editor but crashes when compiled to standalone.
The issue appears to be caused by enabling and disabling GUI components.
I get the following error in the player.log
Receiving unhandled NULL exception
Obtained 12 stack frames.
but no stack info is included in the log (is it saved somewhere else?)
I cannot consistently reproduce the problem in a test project but I can make the problem go away in my project by removing the commands to enable and disable the GUI objects.
Is this a known issue or does anyone know where I can look to investigate what is going on?
I'm building for OSX
Answer by acpirate · Dec 07, 2015 at 02:34 PM
looks like the issue is answered here: Unity bug that wasn't fixed
http://answers.unity3d.com/questions/928486/standalone-mac-build-crashes-on-osx-1010.html
Your answer
Follow this Question
Related Questions
Unity 5 stops responding when i click "open other" project 0 Answers
How to force my *.exe to crash 1 Answer
Windows Standalone crashing silently during scene switching 2 Answers
Fallback handler could not load library Contents/Frameworks/MonoEmbedRuntime/osx/kernel32 1 Answer
Unity build crash on other computers. 0 Answers