From: Roger Pack <rogerpack2005@...>
Date: 2008-06-19T11:39:24+09:00
Subject: Re: help me debug my stack trace

Roger Pack wrote:
> So currently ruby is hung using 100% CPU on my machine.
> 
> Some questions:
> 1) does anybody else have this happen to them?
> 2) does anybody else have a chunk of code that reliably causes ruby to
> leak memory?
> 
> Anyway here are some sample stack traces, if anybody has any pointers.
> Thanks!
> -R
> 
>   1  24540            select$UNIX2003:entry
>   1  24523        select$DARWIN_EXTSN:entry
>   1  23368             _sysenter_trap:entry
>   1  22941          ruby_stack_length:entry
>   1  23392                     memcpy:entry
appears that this might be something in common only to mac os 10.5 based 
on this thread [1].  Apparently it returns a 'weird' error message for 
forcedly closed sockets, so ruby just keeps writing to it and writing to 
it [trying to] without successfully writing anything [and select fails, 
etc. etc.]

At least, that's my hypothesis.  Hard to know if we should come up with 
a patch for ruby just to accomodate Leopard.  Except that it's pretty 
common :)
-R

http://www.nabble.com/RabbitMQ-running-at-100--CPU.-td16024387.html
-- 
Posted via http://www.ruby-forum.com/.