Displaying 1 result from an estimated 1 matches for "destroy_worker".
2006 Aug 07
4
Memory leak?
...all
terminate
end
end
If I run this on a few dozen images simultaneously I watch as top
starts slowly requiring more memory for backgroundrb. Dropping into
script/console tells me two things.
For one, MiddleMan.jobs still has every job, despite my terminate()
call. Second, calling destroy_worker on any of these calls, or gc!
(Time.now), does not free up any of the memory, even though the jobs
disappear. GC.start also does not free up any memory.
If you have any advice on this, that would be great.
Thanks,
Joel