# Excessive consumption of memory due to precompiling assets

**URL:** https://meta.discourse.org/t/excessive-consumption-of-memory-due-to-precompiling-assets/402139
**Category:** Support
**Tags:** unsupported-install
**Created:** [4 במאי,‏ 2026,‏ 2:16pm UTC](https://meta.discourse.org/t/excessive-consumption-of-memory-due-to-precompiling-assets/402139 "2026-05-04T14:16:45Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [5 במאי,‏ 2026,‏ 8:06am UTC](https://meta.discourse.org/t/excessive-consumption-of-memory-due-to-precompiling-assets/402139/11 "2026-05-05T08:06:47Z")

</div>

Ah, you saw an OOM, great. That’s definitive. ulimit has nothing to do with this.

Add swap. There’s no reason not to, other than lack of disk space. Add 8G or 16G, try again. You want to get to a working state. Then you can try to measure what process is blowing up, if you wish.

Set up overcommit. It’s good practice, it reduces peak memory problems. You don’t need to understand it or justify it, just do it. It’s part of a good Linux setup. Check first. It’s this easy:

```plaintext
# uname -a
Linux ubuntu-4gb-hel1-1 6.8.0-110-generic #110-Ubuntu SMP PREEMPT_DYNAMIC
 Thu Mar 19 17:16:23 UTC 2026 aarch64 aarch64 aarch64 GNU/Linux
# cat /proc/sys/vm/overcommit_memory
1

```

---

_[View the full topic](https://meta.discourse.org/t/excessive-consumption-of-memory-due-to-precompiling-assets/402139)._