Crash the game after going to another level.

Hello.
I am the developer of the game “POLYGON”:

(not advertising).
Our players face a problem when entering the main menu from a match, that is, when moving to another level.
This does not happen every time, but it depends on the time spent in the game.
If a player has spent a lot of time in the game (more than 10 minutes), they are more likely to get an error.
However, if the player clicks “Close”, the game is not closed. At some points, you have to completely restart the computer, because the task Manager is not called for some reason.

Absolutely all players get this error. Unfortunately, I have to resort to the help of other developers on Unreal Engine.

I’m using UE 4.24.3 from GitHub.
I tried to Google this error, but found absolutely nothing except:

I tried to “pull” changes from the commit fix of this error, but unfortunately I couldn’t solve the problem.
I also tried to switch to 4.25 Preview, but the engine was very unstable there, so this option is not suitable.

I attach all possible error logs that are available.
Please help us.

Thank you very much.

[UE4CC-Windows-614F829D441834992963BFBA4E372F36_0001 - Google Drive][1]

Hello NODARYN,

If you have a good idea how you can replicate this bug you could send it in via the bug submission form this would give you a more direct wire to the unreal dev team.
Just an idea, but if the frequency of this bug depends on the duration of the game running, it might be connected to some memory issue? The error in the picture is one.
Unfortunately I couldn’t find anything in the log file (maybe I overlooked something, there’s an error regarding particles but I don’t think that caused the crash), haven’t looked at the dump file yet.
Just to make things clear for me, this error occurs while you’re transitioning between maps, and trying to load the ‘Main Menu’ level in?

Yes, this happens when switching to a different map.
No, it has nothing to do with particles. I have other logs that don’t have particle errors. If only it were that simple…

I’d make a development export of the same version, run it until it crashes and then look at the log. You’ll probably find the problem in there…

This is a good idea…