[erlang-questions] is anyone else experiencing reliability issues with R15?

[Geoff Cant]

Gah, I'm just in the middle of upgrading production from R14B3 to R15B02.

Do you have process_info(Pid, backtrace) or similar info for these blocked processes? 


One of the changes from R14 to R15 that I hazily recall was the 'don't scan the message queue if you're waiting on a reply with a ref that was just generated' thing that avoids examining long message queues.

> 	• receive statements that can only read out a newly created reference are now specially optimized so that it will execute in constant time regardless of the number of messages in the receive queue for the process. That optimization will benefit calls togen_server:call(). (See gen:do_call/4 for an example of a receive statement that will be optimized.)
> 
> Own Id: OTP-8623
> 

-Geoff

On 2012-09-19, at 13:11 , Rapsey <rapsey@REDACTED> wrote:

> We run a network of custom built streaming servers doing video streaming
> and transcoding of IPTV channels.
> On R14 everything runs great. But switching to R15, gen_servers
> inexplicably block and don't respond to messages, even the console blocks
> and does not respond to input for 30s or so, processes baloon taking up
> large amounts of memory for no reason. All at random times, but gets much
> worse once there are more users connected to the server doing a lot of
> req/s or receiving a lot of data.
> We're running ubuntu server and start erlang with these switches:
> erl +Bd +S 4 +P 1000000 -env ERL_MAX_PORTS 100000 +K true +A 32
> 
> Are we alone having problems with R15? We tried R15B01 and R15B02.
>