# Another memory leak support topic

**URL:** <https://meta.discourse.org/t/another-memory-leak-support-topic/25330>\
**Category:** Support\
**Created:** [2015年二月17日 20:13 UTC](https://meta.discourse.org/t/another-memory-leak-support-topic/25330 "2015-02-17T20:13:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![matt\_mcneil](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/matt_mcneil/32/81135_2.png) [@matt\_mcneil](https://meta.discourse.org/u/matt_mcneil)\
**Post date:** [2015年二月17日 07:58 UTC](https://meta.discourse.org/t/another-memory-leak-support-topic/25330/1 "2015-02-17T07:58:32Z")

</div>

I’ve recently received a flurry of similar errors as well:

![](https://global.discourse-cdn.com/meta/original/3X/6/a/6a87b13c07526ba89a9a10fc879b203938a0fb05.png)

```
root@discourse:~ # free -h
             total used free shared buffers cached
Mem: 2.0G 1.9G 103M 43M 60M 327M
-/+ buffers/cache: 1.5G 492M
Swap: 2.0G 80M 1.9G

```

Swap was set up at the time of those errors. Any suggestions for settings to adjust?

Thanks much.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2015年二月17日 08:01 UTC](https://meta.discourse.org/t/another-memory-leak-support-topic/25330/2 "2015-02-17T08:01:20Z")

</div>

See the pinned topic on the homepage; 1.2 beta 6,7,8 had a severe memory leak from a dependency. Updating to 1.2 beta 9 will fix.

You will need to update from the command line, see below post.

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2015年二月17日 08:01 UTC](https://meta.discourse.org/t/another-memory-leak-support-topic/25330/3 "2015-02-17T08:01:35Z")

</div>

```plaintext
cd /var/docker
git pull
./launcher rebuild app

```

there a memory leak you need to plug

---

<div class="post-metadata">

**Author:** ![matt\_mcneil](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/matt_mcneil/32/81135_2.png) [@matt\_mcneil](https://meta.discourse.org/u/matt_mcneil)\
**Post date:** [2015年二月17日 08:15 UTC](https://meta.discourse.org/t/another-memory-leak-support-topic/25330/4 "2015-02-17T08:15:53Z")

</div>

Thanks for the quick response! (And, sorry not to have seen that pinned topic…)

---

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [2015年二月17日 20:13 UTC](https://meta.discourse.org/t/another-memory-leak-support-topic/25330/5 "2015-02-17T20:13:43Z")

</div>

This topic was split from [https://meta.discourse.org/t/error-message-cannot-allocate-memory-in-logs/20033/9?u=riking](https://meta.discourse.org/t/error-message-cannot-allocate-memory-in-logs/20033/9)

This topic is now closed. New replies are no longer allowed.