[erlang-questions] How to view the content of memory using gdb

Monk Boy boyofmonk@REDACTED
Tue May 21 09:26:19 CEST 2019

 Because the memory suddenly rises , no time to run 'etop'.  I suspect that
the responseof the request is too large, and  the flood-like keep-alive
request caused such a result.

Marc Worrell <marc@REDACTED> 于2019年5月21日周二 下午2:50写道:

> Do you have some other logs?
> Preferably the one where the message below is printed.
> On 21 May 2019, at 05:39, Monk Boy <boyofmonk@REDACTED> wrote:
> #2  0x000000000045806e in erl_exit_vv (n=1, flush_async=flush_async@REDACTED=0,
> fmt=fmt@REDACTED=0x5fbce8 "%s: Cannot %s %lu bytes of memory (of type
> \"%s\", thread %d).\n", args1=args1@REDACTED=0x7fda361ba830,
> args2=args2@REDACTED=0x7fda361ba848)
>     at beam/erl_init.c:2123
> This could be out of memory, but also something else “Cannot %s” …
> If it is OOM then you can easily check the memory usage of beam.smp whilst
> it is running.
> That would give enough hints.
> Also check your running server with ‘etop’.
> Cowboy has configurations max request content length, it will refuse the
> request with a 4xx error.
> Afaik it defaults to 64K for urlencoded bodies and 8M for other bodies.
> - Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20190521/41f31801/attachment.htm>

More information about the erlang-questions mailing list