We have an intermittent crash (0xC0000005 exception) in packaged builds, that appears to be more frequent on slower systems. Here’s the callstack:
game.exe!TArray<class TWeakPtr<class FActiveTimerHandle,0>,class FDefaultAllocator>::RemoveAll<class <lambda_932268adcceda474c61570d54984ff7e> >(class <lambda_932268adcceda474c61570d54984ff7e> const &) C++
game.exe!FSlateApplicationBase::AnyActiveTimersArePending(void) C++
game.exe!FSlateApplication::TickApplication(enum ESlateTickType,float) C++
game.exe!FSlateApplication::Tick(enum ESlateTickType) C++
game.exe!FEngineLoop::Tick(void) C++
game.exe!GuardedMain(wchar_t const *,struct HINSTANCE__ *,struct HINSTANCE__ *,int) C++
game.exe!GuardedMainWrapper(wchar_t const *,struct HINSTANCE__ *,struct HINSTANCE__ *,int) C++
game.exe!WinMain () C++
This appears to be happening around line 107 in SlateApplicationBase.cpp. I checked the logs and just before the crash we are getting
LogHttp: Warning: InternetStatusCallbackWinInet: on invalid request 000002B33C4A1600.
twice. In case that is relevant. In the same vein, we also occasionally get crashes where our httprequest pointers have gone invalid, but I’ve looked at the entire code chain and don’t see how that could happen what with there being a bunch of shared pointers to the request, and checking for validity before using it, etc. Been a bit of a brain tease.