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.
1 Like
[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
Hi Epic Team,
I am also facing the same issue since v41.00. The UEFN keeps crashing with OoM issue, along with Epic Games Launcher. The VsCode Verse extenstion also keeps crashing and reloading. I can see that it is being recommended to increase the virtual page size, sorry but that is not the right solution. Epic should fix this issue on their end as soon as possible. It is very hard to work on the projects right now
I have noticed something, which might help you guys narrow down the issue. The crash only happens when the VsCode is opened. I noticed that the Verse extensions continuously crashes the VsCode’s extension host program, and tries to restart. I think, in the process, the Verse server in the Unreal Engine is not able to handle this correctly and leads to assertion in the code, crashing UEFN. It also crashes Epic Games launcher
1 Like
Same issue. Ryzen 9 12-core. 128gb of ram. RTX3090 24gb of Vram. Problem runs into hour/s into the project. I suspect there is a memory leak somewhere. Strangely enough the lack of memory is not reflected in my task manager. I have plenty of excess memory when i get that error message.
1 Like
Exactly!! you are spot on. It is definitely a memory leak, and I also do not see memory spike in the performance stats but my computer does slow down a lot. It is so frustrating, and yet no response from Epic Games
1 Like
For anyone getting this who would like to share their logs with us:
- Open the project you have in your logs.
- Tell us exactly what actions you took (I did nothing, I did x,y,z, etc…)
- Please give us specifics and the fewest steps
The editor has many different systems that can be used in various ways, so we need to attach a repro to our tooling so we can track the cause of any leak.
Unfortunately, we are unable to act on a screenshot alone.
When I open multiple VS Code projects for UEFN, the commit size of each code.exe increases by tens of GB while working. Eventually, Windows runs out of committed memory and UEFN/Fortnite crashes with “Out of video memory” or “The paging file is too small.”
Looks like it has something to do with VS Code.
The workaround I found is to close and reopen VS Code when I notice the commit size has increased significantly. Then the commit size is back to normal until i open another VS project and start working then it will increase again.
You can check commit size in details of Task manager, 2 code.exe using almost 100GB is not normal.
Since the 41.00 version update, this issue has persisted. In my case, it happens every time I open a specific project.
Specific operational steps:
- Opening a specific project in the project browser (which I am currently developing, and this issue has indeed blocked my development progress to some extent)
- Wait for the editor until the “Preparing Construction Scripts” in the bottom right corner is executed to the last few (usually within the last ten)
- The engine crashed.
The problem seems to only occur on certain specific projects. If you try to open other projects, such as the provided template project, they can be opened normally.
The good news is that after continuous exploration, I have also successfully found a way to avoid the above problems, which can give me a chance to successfully open the corresponding project. The specific operation is as follows:
- Create a sample project through the Project Browser. In my experience, the success rate of “Survival Island”, “Rivers Edge Island”, and “Tilted Towers POI Island” in the island template is higher.
- Wait for the example project to be created and rebuild Landscape actors (I’m not sure if this step is necessary), then use the New/Open Project option in the Project option of the example project to open the previously unsuccessful projects
- Waiting for the project to open and complete, the ‘Preparing Construction Scripts’ in the bottom right corner will execute successfully, and the engine will not crash
To be honest, I am not sure about the principle behind this, but after multiple attempts, this approach has indeed enabled me to successfully open the corresponding project and continue working. I can provide the screen recording and engine logs of my operation, hoping that the information I provide will be helpful in fixing this issue.
Logs.7z (18.2 MB)
The issue seems to be a memory-leak related to the VSCode Verse Extension. Here’s a video demonstrating it:
The video shows that every time I save a new line into the verse file the committed memory of Code.exe goes up (memory leak). Eventually the system becomes unstable and things start crashing. Sometimes it’s an “out of VRAM” error, other times it can be a pagefile-related error.
Logs attached:
Logs.zip (513.3 KB)
1 Like
Thank you @Caiden
I was able to replicate the same leak locally.
It only happens with Lore extension enabled.
As a workaround you can disable the Lore extension until a fix can be developed and released.
2 Likes
Excellent! I can confirm that disabling the Lore extension fixes the memory leak.
1 Like