Thanks. Memory leak debugging with Rails is difficult. Unfortunately, slower leaks are even harder to find and harder to verify as fixed, but we'll find it and fix it.
Scott On 8/7/06, Steve Longdo <[EMAIL PROTECTED]> wrote: > I've done a quick write up about this on my blog. I've also been doing some > preliminary memory profiling. I'll be writing more about that soon. > > http://www.stevelongdo.com/articles/2006/08/04/typo-4-0-and-memory-reduction > > > -- > Thanks, > -Steve > http://www.stevelongdo.com > > On 8/7/06, mathew <[EMAIL PROTECTED]> wrote: > > Paul Barry wrote: > > > Almost a week later here's what the memory usage looks like: > > > > > > root 3395 0.1 58.0 76412 54980 ? S Aug02 14:07 > > > /usr/bin/ruby /usr/bin/mongrel_rails start > > > > > > So no one else is having problems with this? I gonna have to put in a > > > cron job to restart this weekly, since it's obviously leaking memory. > > > > One of my dispatch.cgis has gone up to 58128 70392, the other has gone > > down to 49308 61572. I think the one that's elevated is because I'm > > logged in to tracks, however. > > > > I don't use Mongrel, maybe that's the difference? > > > > > > mathew > > _______________________________________________ > > Typo-list mailing list > > [email protected] > > http://rubyforge.org/mailman/listinfo/typo-list > > > > > > > > > _______________________________________________ > Typo-list mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/typo-list > > _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
