On 2/4/08, Noah Horton <[EMAIL PROTECTED]> wrote: > 3) I seemed to have a memory leak the first time I deployed, where the > processes kept growing in a stair-step pattern of 50 meg stairs. My best > hypothesis is that objects passed into ask_worker get kept in some > datastructure that never goes away, and thus if you pass any objects there, > things balloon; is that correct? If not, do you have any thoughts on common > 'gotchas' that could cause memory growth?
With an old version I found that I had to explicitly call #kill at the end of the task, or the object would sit around forever. I don't think there's an equivalent in the new version, or what version you're running, so I've no idea if that will solve your question. -Ian _______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
