Search Issue Tracker
Duplicate
Votes
0
Found in
Issue ID
1399455
Regression
No
Fatal Error crash on the editor on a Mac results in an Abort on destruct
When a crash of type "Fatal Error" occurs in the editor, the editor tries to handle the error. However during it's destruction, an abort signal is sent and the clean up doesn't complete properly.
This only seems to occur on a Mac.
Call stack:
__pthread_kill (@__pthread_kill:6)
pthread_kill (@pthread_kill:65)
abort (@abort:41)
abort_message (@abort_message:59)
demangling_terminate_handler() (@demangling_terminate_handler():66)
_objc_terminate() (@_objc_terminate():35)
std::__terminate(void ()()) (@std::__terminate(void ()()):8)
std::terminate() (@std::terminate():16)
__clang_call_terminate (@__clang_call_terminate:7)
GfxDoubleCache<unsigned long, unsigned long long, GfxGenericHash<unsigned long>, std::__1::equal_to<unsigned long>, GfxDoubleCacheConcurrencyPolicy::LocklessGet, GfxDoubleCacheDefaultEmptyDeletedGenerator<unsigned long>, (MemLabelIdentifier)83>::~GfxDoubleCache() (/Users/kara.virgo-ammann/unity/Runtime/GfxDevice/utilities/GfxDoubleCache.h:153)
GfxDoubleCache<unsigned long, unsigned long long, GfxGenericHash<unsigned long>, std::__1::equal_to<unsigned long>, GfxDoubleCacheConcurrencyPolicy::LocklessGet, GfxDoubleCacheDefaultEmptyDeletedGenerator<unsigned long>, (MemLabelIdentifier)83>::~GfxDoubleCache() (/Users/kara.virgo-ammann/unity/Runtime/GfxDevice/utilities/GfxDoubleCache.h:151)
__cxa_finalize_ranges (@__cxa_finalize_ranges:91)
exit (@exit:21)
LaunchBugReporter(BugReportMode, dynamic_array<core::basic_string<char, core::StringStorageDefault<char> >, 0ul> const&) (/Users/kara.virgo-ammann/unity/Editor/Platform/OSX/BugReportingTools.mm:74)
LaunchBugReporter(BugReportMode) (/Users/kara.virgo-ammann/unity/Editor/Platform/OSX/BugReportingTools.mm:42)
EditorMonoConsole::LogToConsoleImplementation(CppLogEntry&) (/Users/kara.virgo-ammann/unity/Editor/Src/EditorMonoConsole.cpp:753)
EditorMonoConsole::LogToConsoleImplementation(DebugStringToFileData const&) (/Users/kara.virgo-ammann/unity/Editor/Src/EditorMonoConsole.cpp:657)
LogToConsoleImplementation(DebugStringToFileData const&) (/Users/kara.virgo-ammann/unity/Editor/Src/EditorMonoConsole.cpp:793)
DebugStringToFilePostprocessedStacktrace(DebugStringToFileData const&) (/Users/kara.virgo-ammann/unity/Runtime/Logging/LogAssert.cpp:993)
DebugStringToFile(DebugStringToFileData const&) (/Users/kara.virgo-ammann/unity/Runtime/Logging/LogAssert.cpp:1073)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build for iOS with UnityAds fails with linker failures when performing a CocoaPods build
- NavMeshManager.LoadData takes a long time and causes performance spikes when enabling a NavMeshSurface with already instantiated NavMeshLinks
- Shadows created by real-time Spotlights are rendered at a very low resolution on terrain when HDRPAsset Lit Shader Mode is set to Forward or Both
- “STP” in Project window > Advanced Upscalers by Priority menu list is shown as available to add when it is already added to the list
- Rename fails with an error “Canceling DisplayDialog” when renaming a Mipmap Limit Group in Project Settings > Quality after adding a new group
This is a duplicate of issue #1399467