[erlang-questions] memsup bug?

Max Lapshin <>
Sun Mar 1 12:19:56 CET 2015


Yes, this becomes very often bug:

2015-03-01 06:11:29 =CRASH REPORT====

  crasher:

    initial call: memsup:init/1

    pid: <0.234.0>

    registered_name: memsup

    exception exit:
{{badarg,[{erlang,cancel_timer,[undefined],[]},{memsup,handle_info,2,[{file,"memsup.erl"},{line,471}]},{gen_server,try_dispatch,4,[{file,"gen_server.erl"},{line,593}]},{gen_server,handle_msg,5,[{file,"gen_server.erl"},{line,659}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]},[{gen_server,terminate,7,[{file,"gen_server.erl"},{line,804}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,237}]}]}

    ancestors: [os_mon_sup,<0.231.0>]

    messages: []

    links: [<0.232.0>,<0.235.0>]

    dictionary: [{system_memory_high_watermark,set}]

    trap_exit: true

    status: running

    heap_size: 2586

    stack_size: 27

    reductions: 12153

  neighbours:



I can fix memsup from all these erlang:cancel_timer(undefined), but I need
to know if this patch is welcome?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150301/8d04161b/attachment.html>


More information about the erlang-questions mailing list