There were several reports from employees experiencing crashes when closing the title.
Hi Michał,
Do you happen to have any more information on the crashes (callstacks, log errors, repro steps, etc)?
Hello Nick,
Here you can see the callstack:
FStreamable::FreeHandles+0x103 - Z:\UEVFS\Root\Engine\Source\Runtime\Engine\Private\StreamableManager.cpp 1439 FStreamableManager::~FStreamableManager+0x278 - Z:\UEVFS\Root\Engine\Source\Runtime\Engine\Private\StreamableManager.cpp 1498 UAssetManager::~UAssetManager+0x124 - Z:\UEVFS\Project\Intermediate\Build\Win64\Project\Inc\Engine\UHT\AssetManager.gen.cpp 274 UAssetManager::scalar deleting destructor’+0x14 -
FObjectPurge::DestroyObjects+0x2bc - Z:\UEVFS\Root\Engine\Source\Runtime\CoreUObject\Private\UObject\GarbageCollection.cpp 875
IncrementalDestroyGarbage+0xdc3 - Z:\UEVFS\Root\Engine\Source\Runtime\CoreUObject\Private\UObject\GarbageCollection.cpp 5012
IncrementalPurgeGarbage+0x3f6 - Z:\UEVFS\Root\Engine\Source\Runtime\CoreUObject\Private\UObject\GarbageCollection.cpp 4671
PurgeAllUObjectsOnExit+0x34d - Z:\UEVFS\Root\Engine\Source\Runtime\CoreUObject\Private\UObject\GarbageCollection.cpp 6278
StaticExit+0x1ae - Z:\UEVFS\Root\Engine\Source\Runtime\CoreUObject\Private\UObject\Obj.cpp 5604
Invoke+0x3 (Inline Function @ 00007ff7ac5ad5a7) - Z:\UEVFS\Root\Engine\Source\Runtime\Core\Public\Templates\Invoke.h 47 UE::Core::Private::Tuple::TTupleBase<TIntegerSequence<unsigned int> >::ApplyAfter+0x4 (Inline Function @ 00007ff7ac5ad5a7) - Z:\UEVFS\Root\Engine\Source\Runtime\Core\Public\Templates\Tuple.h 320
V::TBaseStaticDelegateInstance::ExecuteIfSafe+0x7 - Z:\UEVFS\Root\Engine\Source\Runtime\Core\Public\Delegates\DelegateInstancesImpl.h 801
TMulticastDelegateBase::Broadcast+0x9f (Inline Function @ 00007ff7ac5a010d) - Z:\UEVFS\Root\Engine\Source\Runtime\Core\Public\Delegates\MulticastDelegateBase.h 258 TMulticastDelegate<void __cdecl(void),FDefaultDelegateUserPolicy>::Broadcast+0xad - Z:\UEVFS\Root\Engine\Source\Runtime\Core\Public\Delegates\DelegateSignatureImpl.inl 1080 FEngineLoop::AppPreExit+0x125 - Z:\UEVFS\Root\Engine\Source\Runtime\Launch\Private\LaunchEngineLoop.cpp 6964 FEngineLoop::Exit+0x527 - Z:\UEVFS\Root\Engine\Source\Runtime\Launch\Private\LaunchEngineLoop.cpp 5197 EngineExit+0x18 (Inline Function @ 00007ff7b51d392d) - Z:\UEVFS\Root\Engine\Source\Runtime\Launch\Private\Launch.cpp 71
GuardedMain::__l2::EngineLoopCleanupGuard::{dtor}+0x29 (Inline Function @ 00007ff7b51d392d) - Z:\UEVFS\Root\Engine\Source\Runtime\Launch\Private\Launch.cpp 129 GuardedMain+0x4cd - Z:\UEVFS\Root\Engine\Source\Runtime\Launch\Private\Launch.cpp 201 GuardedMainWrapper+0x1a - Z:\UEVFS\Root\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp 124 LaunchWindowsStartup+0x1f8 - Z:\UEVFS\Root\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp 278 WinMain+0x14 - Z:\UEVFS\Root\Engine\Source\Runtime\Launch\Private\Windows\LaunchWindows.cpp 336 invoke_main+0x21 (Inline Function @ 00007ff7bf3d977a) - D:\a_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl 102
__scrt_common_main_seh+0x106 - D:\a_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl 288
kernel32!BaseThreadInitThunk+0x1d -
ntdll!RtlUserThreadStart+0x28 -`As far as repro goes, all users report that this issue occurs when closing the title.
Thank you. Do you also happen to have the ‘exception error message’? This is typically the last error message in the log, for example: 'Exception Access Violation at address …
Thank you. This looks like one of the streamable handles stored in the manager is no longer pointing to valid memory. Judging by the line number in the call-stack It looks like an active handle.
Were you able to reproduce this with a debugger attached?
Thanks for letting me know. Let me know if you are able to reproduce it in the debugger. It would be good to know which handle is pointing to invalid memory.
I’m sorry for the delay. Here is the error message:
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000001e133bdf222
Unfortunately, I was unable to reproduce this issue. Furthermore, it appears that it is no longer occurring on our end.