[Critical] UEFN Crashing regularly since 41.00 with excessive memory usage

What size is your Windows page file?

It’s any of my projects, currently working on 3 and they all crash when I have vscode open more than a handful of seconds.

Two of them are not published, but here is the code for the one that is public: 0678-0014-4695

1 Like

Same issue here, a project with barely any assets, editor is using 12+ Gigabytes of memory and crashing upon launch without any error message other than ‘‘Sorry, fortnite has crashed’’ default message, wasnt happening in the previous version.

1 Like

How much ?

I am also experiencing the same issue in a specific project. Therefore, as a temporary workaround, I am running the editor in DX11 mode. I do not encounter memory issues in DX11.

[2026.06.25-08.53.26:944][954]LogLandscape: Display: Landscape edit layers merge requires a minimum batch size of resolution 2017x2017, which is higher than the current desired maximum batch resolution 1024x1024. Consider adjusting the maximum batch resolution (landscape.BatchedMerge.MaxResolutionPerRenderBatch) or make sure the landscape edit layers renderers in use require smaller work area.
[2026.06.25-08.53.28:973][954]LogD3D12RHI: Error: pSet->Open() failed
at Z:\UEVFS\Root\Engine\Source\Runtime\D3D12RHI\Private\D3D12Residency.h:151
with error E_OUTOFMEMORY

[2026.06.25-08.53.34:978][954]LogD3D12RHI: Error: Video Memory Stats from frame ID 27584753882300519:
[2026.06.25-08.53.34:981][954]LogD3D12RHI: Error: Local Budget: 0.00 MB
[2026.06.25-08.53.34:981][954]LogD3D12RHI: Error: Local Used: 0.00 MB
[2026.06.25-08.53.34:981][954]LogD3D12RHI: Error: System Budget: 0.00 MB
[2026.06.25-08.53.34:981][954]LogD3D12RHI: Error: System Used: 0.00 MB
[2026.06.25-08.53.34:981][954]LogMemory: Platform Memory Stats for WindowsEditor
[2026.06.25-08.53.34:981][954]LogMemory: Process Physical Memory: 16866.29 MB used, 16866.82 MB peak
[2026.06.25-08.53.34:981][954]LogMemory: Process Virtual Memory: 21699.05 MB used, 21700.36 MB peak
[2026.06.25-08.53.34:981][954]LogMemory: Physical Memory: 24114.04 MB used, 8516.43 MB free, 32630.47 MB total
[2026.06.25-08.53.34:981][954]LogMemory: Virtual Memory: 31217.82 MB used, 6386.64 MB free, 37604.47 MB total
[2026.06.25-08.53.34:981][954]LogWindows: Error: appError called: Fatal error: [File:Z:\UEVFS\Root\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 815]
Out of video memory trying to allocate a rendering resource

41.1 seems worse than 41.0. Over 20GB of memory for UEFN and Fortnite combined now and 50% of CPU. I have a 13th gen i9.. I can’t imagine what is going to happen to people that have been trying to get by on less. You guys need to update your site to note that UEFN and Fortnite will NOT run on anything less than 64GB (instead of 32GB as it says now) and a high power CPU.

On a side note, Firefox is sitting that high due to being on Epic’s site, the pages on the site CONSTANTLY consume too much until the tab crashes. I don’t even know where to post that particular bug, it’s side wide.

2 Likes

I’m having these exact issues aswell.

Exact same issues too. Cant even simply drag and drop a new prop into my game without it taking 1-2 minutes of the editor completely frozen (and occasional system freezing) just to place that single prop. Same case could be said for deleting the object as well.
(Scrolling & searching through the content drawer also does the same thing, lag, tanks computer performance, emits results)

Yeah, I constantly get the out of video memory error now after a bit of time in the editor. I think it’s a memory leak that’s causing all of this.

1 Like

This is the amount of memory usage before opening a project. This is just the plain editor using this amount of memory while waiting for me to choose a project. After opening my project, it’s about 1-2 GB added, so it sums up to around 8 GB in total of memory usage. A huge chunk seems to be a leak in the editor itself and not in any of the projects. Starting a test session fills the memory to 100%+ and we have a crash. I have only 16 GB RAM, but as the thread says, this has not been an issue before 41.00, even for 16 GB RAM.

2 Likes