See the UDN question (duplicated below). I think we need to better manage the lifetime of the event we use for synchronization here.
We are experiencing an issue where when FPlatformMisc::RequestExit or any other function that exits the app is called, render thread waits indefinitely for FrameReadyEvent in FMetalDeviceContext::EndDrawingViewport. FrameReadyEvent is not fired because since FPlatformMisc::RequestExit has been called, IsEngineExitRequested() returns true and FIOSFramePacer::signal function (IOSPlatformFramePacer.cpp) returns prematurely before reaching the event firing logic (at line 118).
Simply changing ListeningEvents to always fire solves the issue for now (like in the following snippet) but what would be the proper way to handle it?
// during shutdown, this can cause crashes (only non-backgrounding apps do this) if (IsEngineExitRequested()) { for( auto& NextEvent : ListeningEvents ) { NextEvent->Trigger(); } return; };
I am not able to find world outliner how to enable it?
How to achieve HLSL Multiple Render Target in Material blueprints?
I'm working on a VR Project and I cannot add Nav Mesh to the stairs??
How can i modify the param name in EQS node
Error: Epic Games Launcher display like
What method is used to fill polygonal regions when drawing spline mesh at run time?
How to properly terminate the DoWork thread function in FAsyncTask?
What property of the Slider is the image used when dragging?
What properties of the progress bar can be used for drag and drop highlighting?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-159215 in the post.
2 |
Component | UE - Platform - Apple |
---|---|
Affects Versions | 4.27 |
Target Fix | 5.6 |
Created | Jul 12, 2022 |
---|---|
Updated | Oct 25, 2024 |