Regression bug: Engine crash when unloading streaming level

In my game, when i unload two streaming levels, the game always crash. So far i’ve only been able to reproduce this in my game. If i take the same unload code, and dump into a blank project with two dummy streaming levels, it works as intended.

When the engine does crash in my game, it doesn’t list any errors or warnings in the log, and the crash dump doesn’t really tell me much. Is there a way to turn on some additional info, so i can see what part of the engine that crashes?

My next step will be to try migrate some of the assets over into the blank project and see if i can reproduce it in a controlled environment where i can share the project with Epic Staff to look into.

Should also mention that my game works just fine in 4.18.3, and it’s a VR game (and i have LateUpdate turned off currently for MotionControllers due to another (hopefully?) known bug)

Will update this later when i get home and can provide some more info.

A bit more info:
I now got home and migrated the two levels into an empty project. There i can’t reproduce it either, so that led me to try something else. I went back to my game project and triggered the start game sequence without using my 3d widget menu, and then it runs fine (no crash), which means that right now i only get it when i click the menu manually.

Will update shortly if i find more.

Hello,

We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.

https://forums.unrealengine.com/unreal-engine/announcements-and-releases/1410408-unreal-engine-bug-submission-form

Thanks

Update2: oh i feel a bit stupid now… reason it didn’t work with my game, was that the pawn which i checked motioncontrollers had late update disabled, was the gameplay pawn, and since i use a different pawn for menu, i forgot to check that as well. Duh! So this is infact just the same known bug with the late update.

Im leaving this open for now, in case someone stumbles over it. And will close it once that bug has been fixed, hopefully in 4.19.1?

Ah, in that case, i’ll just close this again, since i found the reason for it. Im quite sure you guys know about this already (engine that crashes presumably because of some rendering bug with late update turned on).