Main thread crashes after switching to 2018.4 from 2017.4

Unity Engine
,
1

Hi,

This crash started after the major LTS upgrade and switching to Net 4.0 backend from 3.5.

Crashed: com.apple.main-thread
0 appname                   0x10103d490 core::hash_set<core::pair<core::basic_string<char, core::StringStorageDefault<char> > const, int, true>, core::hash_pair<core::hash<core::basic_string<char, core::StringStorageDefault<char> > >, core::basic_string<char, core::StringStorageDefault<char> > const, int>, core::equal_pair<std::__1::equal_to<core::basic_string<char, core::StringStorageDefault<char> > >, core::basic_string<char, core::StringStorageDefault<char> > const, int> >::node* core::hash_set<core::pair<core::basic_string<char, core::StringStorageDefault<char> > const, int, true>, core::hash_pair<core::hash<core::basic_string<char, core::StringStorageDefault<char> > >, core::basic_string<char, core::StringStorageDefault<char> > const, int>, core::equal_pair<std::__1::equal_to<core::basic_string<char, core::StringStorageDefault<char> > >, core::basic_string<char, core::StringStorageDefault<char> > const, int> >::lookup<core::basic_string<char, core::StringStorageDefault<char> > >(core::basic_string<char, core::StringStorageDefault<char> > const&) const + 658 (hash_set.h:658)
1  ourawesomeapp                   0x10103a9ec MonoManager::GetScriptingClass(char const*, char const*, char const*) + 308 (hash_set.h:308)
2  ourawesomeapp                   0x100c3b174 InitializeCoreScriptingClasses() + 24 (CoreScriptingClasses.cpp:24)
3  ourawesomeapp                   0x100c3b0e4 GetCoreScriptingClassesPtr() + 1909 (CoreScriptingClasses.cpp:1909)
4  ourawesomeapp                   0x100c3ac60 Scripting::UnityEngine::ApplicationProxy::Internal_ApplicationWantsToQuit(ScriptingExceptionPtr*) + 718 (CoreScriptingClasses.cpp:718)
5  ourawesomeapp                   0x100fa5fa0 NotifyPlayerQuit(bool) + 298 (Player.cpp:298)
6  ourawesomeapp                   0x100fa6784 PlayerCleanup(bool) + 570 (Player.cpp:570)
7  ourawesomeapp                   0x1011c8f68 UnityCleanup + 224 (LibEntryPoint.mm:224)
8  ourawesomeapp                   0x1009e3874 -[UnityAppController applicationWillTerminate:] + 406 (UnityAppController.mm:406)
9  ourawesomeapp                   0x1016e00b8 -[OneSignalAppDelegate oneSignalApplicationWillTerminate:] + 284 (UIApplicationDelegate+OneSignal.m:284)
10 UIKitCore                      0x2416fbe24 -[UIApplication _terminateWithStatus:] + 220
11 UIKitCore                      0x240fb8bdc __98-[__UICanvasLifecycleMonitor_Compatability deactivateEventsOnly:withContext:forceExit:completion:]_block_invoke.261 + 344
12 UIKitCore                      0x2416fffdc _runAfterCACommitDeferredBlocks + 296
13 UIKitCore                      0x2416eeb2c _cleanUpAfterCAFlushAndRunDeferredBlocks + 352
14 UIKitCore                      0x24171b744 _afterCACommitHandler + 116
15 CoreFoundation                 0x21553889c __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 32
16 CoreFoundation                 0x2155335c4 __CFRunLoopDoObservers + 412
17 CoreFoundation                 0x215533b40 __CFRunLoopRun + 1228
18 CoreFoundation                 0x215533354 CFRunLoopRunSpecific + 436
19 GraphicsServices               0x21773379c GSEventRunModal + 104
20 UIKitCore                      0x2416f4b68 UIApplicationMain + 212
21 ourawesomeapp                   0x1009ce3c0 main + 41 (main.mm:41)
22 libdyld.dylib                  0x214ff98e0 start + 4

I assume it occurs at game launch because no logs are attached to these exceptions what-so-ever, however failed to reproduce.

Any ideas?

2

Any Unity folks that can check those lines causing exception?