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

Valentin Nechayev <>
Fri Apr 27 18:21:57 CEST 2012


Hi,

 Fri, Apr 27, 2012 at 19:21:33, netch wrote about "Re: strange VM hangup with mremap() cycle (R14B04)": 

> Date: Fri, 27 Apr 2012 19:21:33 +0300
> From: Valentin Nechayev <>
> To: 
> Subject: Re: strange VM hangup with mremap() cycle (R14B04)
> 
>  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)
> ()1> erlang:process_info(pid(0,251,0),message_queue_len).
> {message_queue_len,97676}
> ()2> erlang:process_info(pid(0,251,0),message_queue_len).
> {message_queue_len,98505}
> ()3> erlang:process_info(pid(0,251,0),message_queue_len).
> {message_queue_len,98741}
> ()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-


-netch-



More information about the erlang-questions mailing list