Forum: Ruby on Rails Tips on finding memory leaks

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Steven Mohapi-Banks (Guest)
on 2005-12-12 20:22
(Received via mailing list)
Hi all,

Despite going through a pretty comprehensive test cycle and doing
performance testing on my development server I am seeing my memory
usage on my Textdrive account growing incrementally. My process takes
about a week to hit 45mb from a start of around 30.

I'm not really sure where to start looking, as my suspected actions
run fine in development even bashing them with curl for a couple of
hours solid.

Are there any "gotchas" or typical things I should be looking for as
far as memory leaks in Rails apps?

Tom W. (Guest)
on 2005-12-12 21:34
(Received via mailing list)
45MB doesn't sound too out of line, especially if it then stays there,
you might check tip number 7 here:

Steven Mohapi-Banks (Guest)
on 2005-12-12 21:46
(Received via mailing list)

I've read Julik's piece several times. We've been very careful during
development to make sure that everything's thoroughly tested, so
seeing this is a bit of a pain.

I'm wondering if making heavyish use of ActionMailer might cause
problems... our app does make use of outgoing mail quite a lot.

I've tested 80% of our actions in development and after 2 hours of
continuous hits at 2 hits per second the fcgi processes never go over
This topic is locked and can not be replied to.