Rust is one of the most memory-hungry games on the market, and that is not a bug. A procedural map, thousands of player structures and streaming assets mean 10–14 GB is normal for it. What is not normal is usage climbing without limit until the game crashes.
| Situation | Usage | Note |
|---|---|---|
| Main menu | 2–3 GB | Only base assets loaded |
| Loading a map | peaks at 12–16 GB | The heaviest moment — this is where crashes happen |
| Playing a fresh server | 8–11 GB | Few structures built yet |
| Playing late in a wipe | 12–16 GB | Thousands of player structures in memory |
| Long session, 4+ hours | climbs 1–3 GB | Build-up; a restart clears it |
Which means: 16 GB is the practical minimum for comfortable play, and 32 GB removes the question entirely. Rust launches on 8 GB but survives on the page file, and you feel that as stutter.
The "disable the page file for performance" advice is a direct route to crashes in Rust. The game allocates with headroom, and when the system has nothing to give, the process dies with an allocation error.
Rust runs on Unity, and Unity periodically pauses the game to release objects it no longer needs. Those pauses are the micro-stutters you feel every few seconds. gc.buffer sets how much memory to hold as headroom before a collection: a bigger buffer means fewer pauses.
gc.buffer 2048| System RAM | gc.buffer |
|---|---|
| 8 GB | 256–512 |
| 16 GB | 2048 |
| 32 GB or more | 4096 |
Do not overshoot: 4096 on an 8 GB machine adds stutter rather than removing it, because you run out of RAM and start paging. Put the value in client.cfg or it resets on next launch.
If a session starts at 9 GB and reaches 15 GB without coming back down, that is memory not being released. You cannot fix it client-side, but you can soften it:
gc.collect. Costs a brief stutter, returns some memory.-high -malloc=system -nolog-malloc=system — system allocator instead of Unity’s internal one. Often reduces both usage and load times.-nolog — skip verbose logging; saves disk writes and buffer memory.-maxMem= is best left unset. Capping memory does not reduce what the game needs; you just get a crash instead of paging.Messages like "out of memory", "Unity: Could not allocate memory", or a silent close during map load. In order:
mdsched.exe. A faulty module produces exactly this kind of random crash.RustClient.exe.On 8 GB — yes, it is the best money you can spend on Rust, more noticeable than a GPU upgrade. Going 8 → 16 GB removes both the paging stutter and the load-time crashes.
16 → 32 GB only shows up late in a wipe on heavily built servers, or if you play with a browser and Discord on a second monitor. Something else matters more: two modules rather than one. Dual-channel gains more than doubling capacity, and costs less.
16 GB is the practical minimum and 32 GB is comfortable. The game runs on 8 GB but leans on the page file constantly, which shows up as stutter and as crashes during map load, especially late in a wipe on heavily built servers.
It is the memory headroom Unity keeps before a garbage collection pause: bigger buffer, fewer pauses. Use 2048 with 16 GB of RAM, 4096 with 32 GB, and no more than 512 with 8 GB — beyond that you start paging and stutter gets worse.
No, they usually hurt. They forcibly evict cache that the game then re-reads from disk, so instead of a speed-up you get extra stutter. Free memory by closing programs, not with "optimizers".
Technically yes, but it does not reduce what the game needs. Hitting an artificial ceiling makes Rust crash instead of using the page file. Configure the page file and lower draw distance instead.