Win10 UE 5.5.3 process idle for 10-15mins before showing UE splash screen

Development Getting Started & Setup
, , ,
1

Hey there!

I am not sure what happened but around 2 weeks ago when I sat down to launch UE from the Epic Launcher… nothing launched.

I thought that maybe it is a hiccup, so after a few minutes I killed the process in the task manager and tried again and again until finally, the splash screen for UE started showing. As long as my computer is running, UE launches completely fine and normal after those first 15 minutes of being stuck after every PC reboot.

UnrealEditor.exe spawns and reaches around 450MB of memory usage when it enters the 10min of idling. It’s like it’s waiting for some kind of timeout and then continues. Regarding that point, I do have some offline mounting points to my fileserver which is not running during my usual work hours and I remember from Houdini that sometimes it will try to access all available disk mounts and if they are offline it has to wait for the timeout to continue. I wonder if that could be something but no real clue to be honest haha

I couldn’t find much online, found one topic related to Windows Defender silently blocking it and tried disabling it but it doesn’t show any effect. I don’t use any other firewall/anti-virus software.

I have scanned the resource monitor for anything odd and noticed a lot of memory hard faults which could mean that my page file is being accessed more often than I would expect. Today, I disabled the page file but the issue still persists.

Nothing seems out of the ordinary and I use my workstation for Houdini, Nuke, Gaea, anything and everything and nothing seems off except UE for the past two weeks.

It’s installed on a healthy NVMe and all files it needs access to are on SSDs/NVMes as well.
No drive shows activity, no thread is working on UE.exe :person_shrugging:

It’s a bit of an odd one to me and I rather ask here in case someone knows what could be happening in the background before I spent more hours fiddling with all kinds of things.

So, if anyone has any ideas, please let me know! I’d very much appreciate the help!

Thank you!!

sys: 3960x Threadripper, 128gig ddr4, 3090

2

Run with the command line argument “-log”, that’ll pop up a second window that should probably tell you whatever it’s waiting on

1 Like
3

Hey eblade!

I was hoping for that kind of simple option to see behind the curtains! Thank you!
I have yet to try it out. Will report back asap!

1 Like
4

Today I tried it finally and here is the 9 minute long wait. From LogInit to LogMemory.

Not sure if anyone knows what could be the cause here:

image
image1281×406 27.1 KB

[2025.03.01-01.19.19:789][  0]LogConfig: Set CVar [[p.chaos.AllowCreatePhysxBodies:1]]                                                                          [2025.03.01-01.19.19:789][  0]LogConfig: Set CVar [[fx.SkipVectorVMBackendOptimizations:1]]                                                                     [2025.03.01-01.19.19:790][  0]LogConfig: CVar [[ds.CADTranslator.Meshing.ActivateThinZoneMeshing:0]] deferred - dummy variable created                          [2025.03.01-01.19.19:790][  0]LogConfig: CVar [[ds.CADTranslator.Stitching.RemoveThinFaces:0]] deferred - dummy variable created                                [2025.03.01-01.19.19:790][  0]LogConfig: Applying CVar settings from Section [Startup_Windows] File [../../../Engine/Config/ConsoleVariables.ini]               [2025.03.01-01.19.19:791][  0]LogConfig: Applying CVar settings from Section [ConsoleVariables] File [Engine]                                                   [2025.03.01-01.19.19:791][  0]LogConfig: Set CVar [[memory.MemoryPressureCriticalThresholdMB:512]]                                                              [2025.03.01-01.19.19:791][  0]LogConfig: Applying CVar settings from Section [ConsoleVariables] File [C:/Users/dzisign/AppData/Local/UnrealEngine/5.5/Saved/Config/WindowsEditor/Editor.ini]                                                                                                                                    [2025.03.01-01.19.19:791][  0]LogInit: Computer:   name                                                                                                     [2025.03.01-01.19.19:792][  0]LogInit: User:       user                                                                                                     [2025.03.01-01.19.19:792][  0]LogInit: CPU Page size=4096, Cores=24                                                                                             [2025.03.01-01.19.19:792][  0]LogInit: High frequency timer resolution =10.000000 MHz                                                                           [2025.03.01-01.28.25:819][  0]LogMemory: Process is running as part of a Windows Job with separate resource limits                                              [2025.03.01-01.28.25:819][  0]LogMemory: Memory total: Physical=127.9GB (128GB approx) Virtual=128.7GB                                                          [2025.03.01-01.28.25:820][  0]LogMemory: Platform Memory Stats for WindowsEditor                                                                                [2025.03.01-01.28.25:820][  0]LogMemory: Process Physical Memory: 617.88 MB used, 637.27 MB peak                                                                [2025.03.01-01.28.25:821][  0]LogMemory: Process Virtual Memory: 732.43 MB used, 738.41 MB peak                                                                 [2025.03.01-01.28.25:821][  0]LogMemory: Physical Memory: 11415.88 MB used,  119530.13 MB free, 130946.01 MB total                                              [2025.03.01-01.28.25:821][  0]LogMemory: Virtual Memory: 14250.52 MB used,  117495.48 MB free, 131746.00 MB total                                               [2025.03.01-01.28.25:822][  0]LogCsvProfiler: Display: Metadata set : extradevelopmentmemorymb="0"
5

And I want to add that it seems to be something Windows related because if I wait 10minutes after booting my workstation and then launch UE it launches normally. I guess, it is the usual Windows fun where something somewhere is suddenly broken :sweat_smile: