Radiant on Mongrel

Is anyone else using the mongrel 0.3.13.3/apache2/radiant combo on RHEL
or FC and getting the memory leaks and mongrel server crashes that I am?
One guy commented that he was getting weird segfaults from mongrel using
this combination too on the mongrel mailing list. It’s seemingly random
and I have yet to be able to reproduce it. If you have a rails
application in production running radiant, go run top and sort by memory
and see if the mongrel running your radiant is upwards of 150+MB of RAM
usage.

Could this be a problem with caching? Garbage collection in mongrel?
Something else? If anyone has any leads or are experiencing the same
things in a production mode deployment I’d like to hear it and see if we
can track it down.

josh @ besquared

Josh, may this thread be of some help?

http://lists.radiantcms.org/pipermail/radiant/2006-July/000763.html

–M

On 8/1/06, Josh F. [email protected] wrote:

Is anyone else using the mongrel 0.3.13.3/apache2/radiant combo on RHEL
or FC and getting the memory leaks and mongrel server crashes that I am?

I running this combination but on FreeBSD and it works fine. I’m now
using apache 2.2 instead of 2.0 but it worked too with 2.0.

roberto 4180 0.0 5.5 32712 28280 ?? S 15Jul06 39:45.82
/usr/local/bin/ruby18 /usr/local/bin/mongrel_rails start -d -e
production