[Backgroundrb-devel] Cleaing up after workers in backgroundrb

[Rue Turner]

On Thu, 2008-03-06 at 13:00 +0530, hemant kumar wrote:

> On Tue, 2008-03-04 at 16:27 -0500, mike bukhin wrote:
> > Hi there--
> > 
> > I just updated to the latest build of Backgroundrb and am hitting up
> > against a memory leak because my workers aren't cleaning up.  My code
> > concurrently pulls a large number of images using RMagick.  I thought
> > the problem was with RMagick but after putting in some garbage
> > collection code when pulling an image, my code runs well from irb.
> > When wrapped with backgroundrb, it eventually hangs.
> > 
> > In the old backgroundrb I had a self.delete at the end of do_work to
> > clean up.  Now my setup is a little different:
> > 
> > MiddleMan.worker(:context_worker).process_context(id)
> > 
> > and then
> > 
> > class ContextWorker < BackgrounDRb::MetaWorker
> > 
> >   set_worker_name :context_worker
> >   pool_size 1
> > 
> > 
> >   def create(args = nil)
> > 
> >   end
> > 
> >   def process_context(id)
> > 
> >      do_stuff()
> > 
> >   end
> > 
> > end
> > 
> > How do I clean up after process_context().
> > 
> 
> You can still call, 'exit' at the end of worker to finish up execution
> of task.
> 
> And what you mean by 'cleanup' actually? RMagick is one heck of a
> library to work with, but if it works at irb prompt, should work in
> BackgrounDRb worker too. Send us the worker code, and we will see whats
> going wrong.
> 
> 
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080306/95941546/attachment.html