On Sat, Nov 29, 2008 at 5:18 AM, Andreas Fuchs <[EMAIL PROTECTED]> wrote: > A little clarification. I have just done a few experiments "on the > wire", and it seems that mem usage for this usage pattern in 1.1 grows > if a worker has reserved a job, and does stats-job on it, which is > exactly the usage pattern that async_observer exhibits. Here's a test > case using the ruby beanstalk-client library:
Hah, I fixed this one without even knowing it :-) My commit to keep all_jobs_used consistent fixes the problem http://github.com/gbarr/beanstalkd/commits/memleak Graham. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
