# Forum Unusable due to "Can’t save in background: fork: Cannot allocate memory”

**URL:** <https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781>\
**Category:** Self-hosting\
**Created:** [22 בפברואר,‏ 2017,‏ 12:17pm UTC](https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781 "2017-02-22T12:17:56Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Goosy](https://avatars.discourse-cdn.com/v4/letter/g/db5fbb/32.png) [@Goosy](https://meta.discourse.org/u/Goosy)\
**Post date:** [22 בפברואר,‏ 2017,‏ 12:17pm UTC](https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781/1 "2017-02-22T12:17:57Z")

</div>

I’m using a 2GB Digital Ocean Droplet and I keep getting 500 errors when users are trying to post new comments.

I checked the server logs and I see them full of these 2 lines:

44:M 22 Feb 12:10:04.079 \* 1 changes in 900 seconds. Saving…  
44:M 22 Feb 12:10:04.079 # Can’t save in background: fork: Cannot allocate memory

Also, when I ssh into my droplet, I see that memory consumption is at 82%.

I tried updating everything to latest, resetting the machine, but nothing helps on the long run. It works ok for a bit an then starts throwing the errors again.

---

_[View the full topic](https://meta.discourse.org/t/forum-unusable-due-to-can-t-save-in-background-fork-cannot-allocate-memory/57781)._
