Previously posted on ruby talk. Response...silence :)
..
Perhaps someone out there can help give me a clue about the following
situation:
My mongrel processes seemed to be leaking.
As an example of this, if I added this code to the bottom of
environment.rb
Thread.new {loop do; print 'w'; end
Maybe the upgrade installed fastthread?
Most likely though it's related to the Rails app itself, not Mongrel,
and isn't immediately reproducible. Cache freshness could have a large
effect on which codepaths get traversed.
What did you add that Thread loop for? I don't understand.
Evan
On Mon, A
On Mon, Apr 28, 2008 at 5:14 PM, Roger Pack <[EMAIL PROTECTED]> wrote:
> Previously posted on ruby talk. Response...silence :)
>
Didn't saw that post, sorry.
> ..
> Perhaps someone out there can help give me a clue about the following
> situation:
>
> My mongrel processes seemed to be le
On Mon, Apr 28, 2008 at 2:23 PM, Evan Weaver <[EMAIL PROTECTED]> wrote:
> Maybe the upgrade installed fastthread?
Could have. Prolly wouldn't have done much since I'm running patch 111.
> Most likely though it's related to the Rails app itself, not Mongrel,
> and isn't immediately reproducible
