Unity Editor crash on start

Hi,

At the moment the Unity Editor 2018.4.3 is crashing on our project if we open the editor the first time. Restarting the editor after the crash is working fine. For us it is a huge problem as our builds are done in a clean workspace and the editor is crashing when opening the project.

We have a hard time to locate the issue.
The call stack from the Editor.log look:

Code (csharp):

1.  
2. ========== OUTPUTTING STACK TRACE ==================
3.  
4. 0x00000001405B6F59 (Unity) GameObject::ActivateAwakeRecursivelyInternal
5. 0x00000001405B6A92 (Unity) GameObject::ActivateAwakeRecursively
6. 0x00000001405B8BB3 (Unity) GameObject::Deactivate
7. 0x00000001408F8F18 (Unity) DestroyObjectHighLevel_Internal
8. 0x00000001408F8D70 (Unity) DestroyObjectHighLevel
9. 0x000000014097E0B4 (Unity) DestroyWorldObjects
10. 0x000000014097DF33 (Unity) DestroyWorld
11. 0x0000000140E6F537 (Unity) EditorSceneManager::NewScene
12. 0x000000014134434E (Unity) RestoreLastOpenedScenes
13. 0x0000000141339AFC (Unity) Application::FinishLoadingProject
14. 0x00000001414A6249 (Unity) WinMain
15. 0x000000014249824A (Unity) __scrt_common_main_seh
16. 0x00007FFC16297BD4 (KERNEL32) BaseThreadInitThunk
17. 0x00007FFC1822CE71 (ntdll) RtlUserThreadStart
18.  
19. ========== END OF STACKTRACE ===========
20.  

I'm not sure what the issue of the stack walker is but the error.log is not helping at all:

Code (csharp):

1.  
2. Stack Trace of Crashed Thread 26952:
3. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00000001405B6F59)
4. 0x00000001405B6F59 (Unity) (function-name not available)
5. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00000001405B6A92)
6. 0x00000001405B6A92 (Unity) (function-name not available)
7. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00000001405B8BB3)
8. 0x00000001405B8BB3 (Unity) (function-name not available)
9. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00000001408F8F18)
10. 0x00000001408F8F18 (Unity) (function-name not available)
11. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00000001408F8D70)
12. 0x00000001408F8D70 (Unity) (function-name not available)
13. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 000000014097E0B4)
14. 0x000000014097E0B4 (Unity) (function-name not available)
15. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 000000014097DF33)
16. 0x000000014097DF33 (Unity) (function-name not available)
17. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 0000000140E6F537)
18. 0x0000000140E6F537 (Unity) (function-name not available)
19. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 000000014134434E)
20. 0x000000014134434E (Unity) (function-name not available)
21. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 0000000141339AFC)
22. 0x0000000141339AFC (Unity) (function-name not available)
23. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00000001414A6249)
24. 0x00000001414A6249 (Unity) (function-name not available)
25. ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 000000014249824A)
26. 0x000000014249824A (Unity) (function-name not available)
27. 0x00007FFC16297BD4 (KERNEL32) BaseThreadInitThunk
28. 0x00007FFC1822CE71 (ntdll) RtlUserThreadStart
29.  

Last Entries in the Editor.log on a build machine are:

Code (csharp):

1.  
2. Initializing Unity extensions:
3.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/Timeline/Runtime/UnityEngine.Timeline.dll'  GUID: 6a10b2909283487f913b00d94cd3faf5
4.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/TestRunner/portable/nunit.framework.dll'  GUID: 405b9b51bb344a128608d968297df79c
5.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/GUISystem/Standalone/UnityEngine.UI.dll'  GUID: f70555f144d8491a825f0804e09c671c
6.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/GUISystem/UnityEngine.UI.dll'  GUID: f5f67c52d1564df4a8936ccd202a3bd8
7.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/Timeline/RuntimeEditor/UnityEngine.Timeline.dll'  GUID: 844f815391db42d49455cbf1a7bfc434
8.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/Networking/Standalone/UnityEngine.Networking.dll'  GUID: dc443db3e92b4983b9738c1131f555cb
9.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/UnitySpatialTracking/Runtime/UnityEngine.SpatialTracking.dll'  GUID: ed7343f30e3843b3afda8f8b02669cea
10.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/UnityGoogleAudioSpatializer/Editor/UnityEditor.GoogleAudioSpatializer.dll'  GUID: 4a3ecb1425d14502837abea459cf2b70
11.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/Networking/Editor/UnityEditor.Networking.dll'  GUID: 5f32cd94baa94578a686d4b9d6b660f7
12.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/UnitySpatialTracking/Editor/UnityEditor.SpatialTracking.dll'  GUID: b5da970776034f77a070d99423d68791
13.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/Networking/UnityEngine.Networking.dll'  GUID: 870353891bb340e2b2a9c8707e7419ba
14.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/TestRunner/UnityEngine.TestRunner.dll'  GUID: 53ebcfaa2e1e4e2dbc85882cd5a73fa1
15.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/UnityGoogleAudioSpatializer/RuntimeEditor/UnityEngine.GoogleAudioSpatializer.dll'  GUID: ead147da21254ff9a0a936bdd75e1680
16.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/UnityGoogleAudioSpatializer/Runtime/UnityEngine.GoogleAudioSpatializer.dll'  GUID: e4f4cf1b9b434137a499903a7a1d651a
17.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/UnityVR/Editor/UnityEditor.VR.dll'  GUID: 4ba2329b63d54f0187bcaa12486b1b0f
18.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/UnitySpatialTracking/RuntimeEditor/UnityEngine.SpatialTracking.dll'  GUID: 3a84de5cd0624681b6b6dcd8921d912a
19.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/GUISystem/Editor/UnityEditor.UI.dll'  GUID: 80a3616ca19596e4da0f10f14d241e9f
20.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/TestRunner/Editor/UnityEditor.TestRunner.dll'  GUID: 4113173d5e95493ab8765d7b08371de4
21.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/TestRunner/net35/unity-custom/nunit.framework.dll'  GUID: 4b3fa4bde7f1451a8218c03ee6a8ded8
22.  '/Applications/Unity_2018.4.3f1/Unity.app/Contents/UnityExtensions/Unity/Timeline/Editor/UnityEditor.Timeline.dll'  GUID: 7668179ede524d6396c8b7d84461ea29
23.  

 

Please check if the crash also occurs with the latest 2018.4 LTS release, it's 2018.4.4 at the time of writing. If the crash persists and is reproducible, please submit a bug-report as described in this document:
https://unity3d.com/unity/qa/bug-reporting

It's important that you report these issues together with a reproduction project if you want them to get fixed. If you don't do it, it might be a long time until someone else reports them or until Unity Technologies find them.

After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. Please post the Case number (number only, not the link) in this forum thread for Unity staff to pick up.

 

Thanks for the fast reply.

Yes it happens with 2018.4.4 as well.
I done now a clean import of all assets without using the unity cash server on an OSX machine. Doing that still results in a crash. There is no indication what could be the cause of the crash.

A bug report requires the upload of the whole project. As we have no clue what is connected to the crash I can't strip down the project. I'll try to uploaded the whole project but it is ~60GB

 

In my case the last open scene was an empty scene. But it happens on all workstations and on the builders. The builders are opening the project in a complete new workspace.

I was now able to get a callstack from one of the builders:

Code (csharp):

1.  
2. Obtained 31 stack frames.
3.  
4. #0  0x00000100c8d58b in CanDestroyObject(Object*, bool)
5. #1  0x00000100c8e235 in DestroyObjectHighLevel(Object*, bool)
6. #2  0x00000100d3718a in DestroyWorldObjects(dynamic_array<int, 0ul> const&)
7. #3  0x00000100d36daf in DestroyWorld(bool)
8. #4  0x0000010137f76b in EditorSceneManager::NewScene(NewSceneParameters const&)
9. #5  0x000001019ce345 in Application::FinishLoadingProject()
10. #6  0x000001007008a2 in -[EditorApplication applicationDidFinishLaunching:]
11. #7  0x007fff2f996af6 in __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__
12. #8  0x007fff2f996a70 in ___CFXRegistrationPost_block_invoke
13. #9  0x007fff2f9969da in _CFXRegistrationPost
14. #10 0x007fff2f99ee88 in ___CFXNotificationPost_block_invoke
15. #11 0x007fff2f9078d4 in -[_CFXNotificationRegistrar find:object:observer:enumerator:]
16. #12 0x007fff2f906c87 in _CFXNotificationPost
17. #13 0x007fff31b7f217 in -[NSNotificationCenter postNotificationName:object:userInfo:]
18. #14 0x007fff2cfc081c in -[NSApplication _postDidFinishNotification]
19. #15 0x007fff2cfc016f in -[NSApplication _sendFinishLaunchingNotification]
20. #16 0x007fff2cfbe2c3 in -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:]
21. #17 0x007fff2cfbdf13 in -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:]
22. #18 0x007fff31bc8d6e in -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:]
23. #19 0x007fff31bc8beb in _NSAppleEventManagerGenericHandler
24. #20 0x007fff30b54397 in aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*)
25. #21 0x007fff30b53c29 in dispatchEventAndSendReply(AEDesc const*, AEDesc*)
26. #22 0x007fff30b53b01 in aeProcessAppleEvent
27. #23 0x007fff2ec28ec7 in AEProcessAppleEvent
28. #24 0x007fff2cfba2f2 in _DPSNextEvent
29. #25 0x007fff2cfb8d93 in -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
30. #26 0x007fff2cfb2eb0 in -[NSApplication run]
31. #27 0x007fff2cfa23f0 in NSApplicationMain
32. #28 0x000001007295dc in EditorMain(int, char const**)
33. #29 0x00000100729a59 in main
34. #30 0x007fff5bdac3d5 in start
35.  

 

What is loaded in Unity when FinishLoadingProject() is called? How can I identify the scene that populated the world before NewScene() is called?

Is there any way to track down the "broken" game object? Like the prefab name or the list of attached components?
For me it looks like there is an GameObject pointer in the "World" array that is not valid any more or is in the process of destroying initiated by another thread.

It would be nice to get any some more information about the loaded content. We are totally in the dark at the moment.

As we are investigating we are getting more information, dumps and logs. I would like to share those with the bug report but I can't find a way to login or to edit the report.
How do I append new information's and resources to a report?

 

If you send a bug report asking for an upload link, you'll usually get somewhere you can put the project.

Bugs does get fixed faster the more things you manage to strip from the repro, but it's not impossible to upload multi-gigabyte projects.

 

I understand that. But we have no clue what assets are involved in the issue.

If you could point out a little more details about the initial asset import process and what assets are loaded into the "World" before the first editor scene is loaded, you would help us a lot.
Can we set a higher loglevel to get more details from unity? Just a list of loaded assets would help us very much to identify the issue and your guys with a stripped version of our project.

 

With some effort we have been able to locate the issue. It was an yaml syntax error in a prefab file.
After we knew what we are looking for we where able to find it in the logfile. With the amount of prefabs in the project it was not easy to locate and impossible to see in the huge log file with out to know what we should look for. Neither the key word's "exception", "error", "warning" or "failed" are used that are common to parse.
We are adding now "Unable" to our log file parser. Do you have a list of unity "breaking" log messages or keywords to parse for in Unity?

Code (yaml):

1. Unable to parse YAML file: [did not find expected ',' or '}'] at line 11
2.  
3. (Filename: C:\buildslave\unity\build\Runtime/Serialize/TransferFunctions/YAMLRead.cpp Line: 210)
4.  
5. Updating Assets/Drive/GameLogic/Season/GameModes/Season/Prefabs/P_Drive_GameLogic_GameModes_SeasonGameMode.prefab - GUID: 8f4d9340c20aea742b4edf7d16392f97...
6. Unable to parse file Assets/Drive/GameLogic/Season/GameModes/Season/Prefabs/P_Drive_GameLogic_GameModes_SeasonGameMode.prefab: [did not find expected ',' or '}'] at line 735
7.  
8. (Filename: C:\buildslave\unity\build\Runtime/Serialize/TransferFunctions/YAMLRead.cpp Line: 206)
9.  
10. Missing GameObject : Unity has detected a Transform component that is not assigned to a GameObject, and has created a new GameObject 'Recovery GameObject (8858458598365043761)' to contain the component.
11. (Filename: C:\buildslave\unity\build\Editor/Src/Utility/DanglingComponentManager.cpp Line: 55)
12.  
13. done. [Time: 32.442200 ms]