[erlang-questions] New Feature added to Erlang
Mon Apr 1 10:51:14 CEST 2013
it's the sasl logging that includes compete state info on a process crash
that can cause the out of memory situation. The error_logger itself is not
Of course, the too_big_to_fail flag will get around the sasl deficiency.
Roll on R18.
On Apr 1, 2013 9:16 AM, "Max Lapshin" <max.lapshin@REDACTED> wrote:
> Nice joke, of course, but still the main reason for erlang application to
> fail is error_logger process.
> Every blog post about erlang starts from word "it is rock solid,
> everything is restarted", but when buggy error_logger is killed after
> eating 10 Gig of RAM, then whole erlang system is down.
> I don't understand what is the problem in restarting error_logger
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions