# Crashing with out of memory error when opening a topic

**URL:** <https://meta.discourse.org/t/crashing-with-out-of-memory-error-when-opening-a-topic/106983>\
**Category:** Product Support\
**Tags:** server-resources\
**Created:** [19.Январь.2019 18:26:53 UTC](https://meta.discourse.org/t/crashing-with-out-of-memory-error-when-opening-a-topic/106983 "2019-01-19T18:26:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ssvenn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ssvenn/32/86740_2.png) [@ssvenn](https://meta.discourse.org/u/ssvenn)\
**Post date:** [19.Январь.2019 19:12:04 UTC](https://meta.discourse.org/t/crashing-with-out-of-memory-error-when-opening-a-topic/106983/3 "2019-01-19T19:12:04Z")

</div>

“failed to allocate memory” sounds like maybe the database is tuned to use too much ram from the previous plan, my empty test instance uses about 1gb on a 4gb centos vm

```
[root@discocent discourse]# free
              total used free shared buff/cache available
Mem: 3881412 912764 413192 33168 2555456 2401820
Swap: 2097148 1544 2095604

```

Does the droplet have any swap configured? Have you tried rebuilding the app container?  
Check for out-of-memory errors in dmesg or /var/log/syslog too

Try to tail -f /var/discourse/shared/standalone/log/rails/production.log when opening a topic and look for error messages there maybe, that log is pretty verbose.

---

_[View the full topic](https://meta.discourse.org/t/crashing-with-out-of-memory-error-when-opening-a-topic/106983)._
