I’ve been setting up a relatively simple scene for a few hours, but after an engine crash, upon reopening my main level, I’m running into an issue where UE runs out of memory during allocation for the paging file. After increasing my page file and looking at others’ solutions to this problem, I tried increasing my page file size in Windows’ Advanced System Settings, but it resulted in no change even with the page file size at 128GB. Multiple restarts of my system have resulted in no changes.
The error message is as follows:
LogWindows: Error: appError called: Fatal error: [File:D:\build++UE5\Sync\Engine\Source\Runtime\Core\Private\GenericPlatform\GenericPlatformMemory.cpp] [Line: 241]
Ran out of memory allocating 67107566064 bytes with alignment 0. Last error msg: The paging file is too small for this operation to complete…
Something odd about this message that I noticed is that I don’t have any such file “build” in my D: drive, but it seems to be referencing it. Additionally, the massive allocation it seems to want (~67GB) is well within the page file size I set. My system specs are as follows:
CPU: i9-10980
GPU: Nvidia RTX 2080 Super
RAM: 32GB
Additionally, my SSD (1.84TB total) has over 800GB of free space, so I can’t imagine that I’m somehow running out of disk space.
I apologize if this is in the wrong forum section; I didn’t see any dedicated forum section to crash/bug assistance.
I have been having the same issue, crashing constantly citing page file issue. I manually set it, have Windows manage it, to no avail. Running an i9 13900k with 128GB of DDR5, a RTX 3090 and plenty of SSD space.
I had the same problem but found a solution for this. This is what worked for me…
Set the virtual memory to more than is currently being used. (had 8GB - 16GB, then Changed it to 32GB - 64GB)
open the baseeditor.ini file located in " UE_5.1\Engine\Config\BaseEditor.ini "
find and edit
MemoryMinFreeVirtual=
MemoryMinFreePhysical=
both to lower but the same numbers, default is 2048 and I set both to 256.
save file.
restart the computer… worked for me…
In my case I’m using the alembic importer, once it is done importing/converting the alemic into a .uasset, it crashes when I try to save it.
It’s also trying to build on D drive, which I’ve even plugged out so it doesn’t access it anymore. Still want’s to put ■■■■ on D drive.
It’s like someone hardcoded the page file to be on D drive.
Obviously I made sure that my page file is big enough.
No success. Can’t import my assets, can’t work on my project until this is fixed.
Oh and I’m using 5.2 seems like this is an issue that persists longer than it should
Description:
While buildning default landscape 2km x 2km map with only a few of my actors added
in log appeared error “Ran out of memory allocating bytes with alignment 1. Last error msg: The paging file is too small for this operation to complete.”
(checking the logs at (the project name)\Saved\Logs).
Solution:
It turned out that HLOD build required up to 50GB ! of temporary disk space (via windows page file; note: the temporary space is then released after the build is done).
The C: partition did not have that much space left so I moved page file to D: partition (see the procedure below).
Windows 10 page file settings:
r.clk on Start
System
Advanced system settings (link on the right - “System properties” dialog appears )
I too ran into this issue several times on different activities in a 64Gb memory system with multiple hard drives. In the end I ended up with 64000 Mb pagefiles, fixed size on three of the hard drives. so 192.000 Gb in total.
I ran into this also, posting this here in case someone has a similar issue. in my case it was an animation blueprint that used an array. anim bps run 100% of the time even when its just the editor and when the game was not running the array was empty so it was constantly spamming error messages in the log saying tried to access index XX from array of length 0. I had a bunch of log files that were like 20 gigs. deleted the log files and fixed the code and that fixed it for me. So, might be worth checking Saved/Logs and make sure you dont have something spamming the log file
