From: akr@...
Date: 2014-02-20T13:23:05+00:00
Subject: [ruby-core:60907] [ruby-trunk - Bug #9525] Stuck with	Socket.pack_sockaddr_in

Issue #9525 has been updated by Akira Tanaka.


Eric Wong wrote:

>  * backwards for loop for list is confusing to me,
>    any reason for not reversing list declaration?

I prefer ordering consistency between "list" and "res".

>  * why xmalloc + MEMZERO?  xcalloc is shorter and generates smaller code

xcalloc is good idea.



----------------------------------------
Bug #9525: Stuck with Socket.pack_sockaddr_in
https://bugs.ruby-lang.org/issues/9525#change-45309

* Author: Naotoshi Seo
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 1.9.3p194
* Backport: 1.9.3: REQUIRED, 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
We met this trouble with Fluentd https://github.com/fluent/fluentd. 

Fluentd is sometimes stuck at `Socket.pack_sockaddr_in` line on shutdown. 
Here is the gist https://gist.github.com/sonots/9047653 to explain details. 





-- 
http://bugs.ruby-lang.org/