Hey guys,
We’ve sent Unity a bug report but since I haven’t heard from them in almost a week I figured I’d ask here.
We’re getting a crash of the Unity Editor when we try to build out game for Standalone (happens for Windows, Mac and Linux builds). About 50% of the time it crashes and the rest of the time it freezes and never completes. It’s happening on two different computers and it’s got us in a jam since we can’t produce new builds of the game currently. Everything works fine in the editor, this is only when we try to build the game.
If anyone has run into this before or can point us in the right direction it would be very helpful.
Ver: Unity Pro v4.2.0
Thanks,
Preston
Below are the seemingly relevant parts the editor.log
System memory in use before: 215.7 MB.
Unloading 70 Unused Serialized files (Serialized files now loaded: 0 / Dirty serialized files: 0)
System memory in use after: 209.0 MB.
Unloading 566 unused Assets to reduce memory usage. Loaded Objects now: 17879.
Total: 18.452082 ms (FindLiveObjects: 0.647827 ms CreateObjectMapping: 0.404477 ms MarkObjects: 4.778741 ms DeleteObjects: 2.343140 ms)
System memory in use before: 427.0 MB.
Crash!!!
SymInit: Symbol-SearchPath: 'C:/Program Files (x86)/Unity/Editor/Data/MonoEmbedRuntime;.;H:\Dropbox\PULSAR_UnityProject;C:\Program Files (x86)\Unity\Editor;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'me_000'
OS-Version: 6.2.9200 () 0x100-0x1
========== OUTPUTING STACK TRACE ==================
(0x0136D759) (Unity): (filename not available): CombineScissorAlpha1 + 0x1459
(0x0136E3DD) (Unity): (filename not available): fxShader_MIX_MUL_CL_SSE2 + 0xad
(0x01347E61) (Unity): (filename not available): cpuShaderThreadKickPending + 0x2d1
(0x0138A9DF) (Unity): (filename not available): algThreadJobQueueRun + 0x4f
(0x01347D50) (Unity): (filename not available): cpuShaderThreadKickPending + 0x1c0
========== END OF STACKTRACE ===========