[erlang-questions] Need help understanding why the error_logger is growing to gigabytes of memory even when idle
Wed Oct 17 04:58:59 CEST 2012
If you have changed some of your busy Erlang processes to run with priority "high", that seems like it could cause the behavior you are seeing.
On 10/16/2012 07:50 PM, Kris Rasmussen wrote:
> Hi All,
> We are observing error_logger processes that use many gigabytes of memory over time. Unfortunately, I don't know how much time it takes for them to get into this state yet, but the memory drops to virtually nothing when we trigger a manual gc cycle. Here is some information about one such process that was using 2+GB of memory before we GC'd it:
> ()23> process_info(whereis(error_logger), [memory, heap_size, total_heap_size, messages, binary, message_queue_len, stack_size, garbage_collection]).
> As you can see, the heap size is much smaller than the total memory. We've read elsewhere that binaries can create problems like this, but I'll admit I don't fully understand the reason. Does anyone have any idea how the error_logger could be using so much memory and what the best approach is to ensure it runs a GC cycle more often? We could simply GC the error_logger with another process more frequently, but I'd rather understand what we are doing to put it in this state first.
> In case it's significant, we have a custom report handler that forwards error_logger messages to log4erl.
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions