[erlang-questions] strange VM hangup with mremap() cycle (R14B04)

[Valentin Nechayev]

 Fri, Apr 27, 2012 at 18:57:26, netch wrote about "strange VM hangup with mremap() cycle (R14B04)": 

> as seen on <strike>national TV</strike> my monitor just now: an Erlang
> VM in out system has hung up, with one thread active and all other
> sleeping. The active thread strace shows:
> 
> 19:45:06.215838 mremap(0x7f47ca48b000, 190615552, 190619648, MREMAP_MAYMOVE) = 0x7f47e5217000

Ha ha, I have reproduced it:

Erlang R14B04 (erts-5.8.5) [source] [64-bit] [rq:1] [async-threads:10] [hipe] [kernel-poll:true]

Eshell V5.8.5  (abort with ^G)
(sysmon41@REDACTED)1> erlang:process_info(pid(0,251,0),message_queue_len).
{message_queue_len,97676}
(sysmon41@REDACTED)2> erlang:process_info(pid(0,251,0),message_queue_len).
{message_queue_len,98505}
(sysmon41@REDACTED)3> erlang:process_info(pid(0,251,0),message_queue_len).
{message_queue_len,98741}
(sysmon41@REDACTED)4> erlang:process_info(pid(0,251,0),backtrace).
<... Here the long timeout is...>
*** ERROR: Shell process terminated! (^G to start new job) ***

Seems the attempt to get backtrace is the trigger.


-netch-