[erlang-questions] Erlang OTP 17.3 memory fragment problem (maybe)

Lukas Larsson garazdawi@REDACTED
Mon Apr 13 09:28:31 CEST 2015

Hello Daniel,

On Mon, Apr 13, 2015 at 3:13 AM, Daniel <liudanking@ <liudanking@REDACTED>
> So my question is:
> Does it means that  I meat a ‘classic' memory fragmentation problem? If
> YES, how can I free the fragment memory to OS?Because my ejabberd have been
> killed by Linux OOM for several times. If NO, what cause the memory
> increase all the time?

Would you mind checking how much of the binary_alloc memory is part of the
mbc pool? ("erlang:system_info({allocator,binary_alloc}).", look for
mbcs_pool). If it is very large you may have hit the bug described in
OTP-12323, which has been fixed in Erlang/OTP 17.4. The scenario you are
describing where the memory utilization constantly decreases sound very
similar to what the bug fixed. If you don't want to upgrade to 17.4, you
can also disable the pool in 17.3.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150413/a8703fca/attachment.htm>

More information about the erlang-questions mailing list