On Thu, Nov 27, 2008 at 5:15 PM, Andreas Fuchs <[EMAIL PROTECTED]> wrote: > > > On Nov 27, 9:31 pm, [EMAIL PROTECTED] wrote: >> On Nov 26, 2008 5:53pm, Andreas Fuchs <[EMAIL PROTECTED]> wrote: >> >> > I'll try and run it under valgrind tomorrow. Maybe the description of >> > our job submission pattern and the library info an help you a bit >> > already. >> >> Today I did find a memory leak when tubes are freed. So if you cause >> tubes to get created and freed on a regular basis you would see memory >> grow. > > That's great news! However, I have only one permanent non-default > tube, just putting jobs into it. (See the stats output above, my > current-tubes is 2).
yeah, it seems like you are putting them in and taking them out. you also seem to be calling stats-job. Is that the worker or the producer doing that ? what is your average/max job size ? do you have binlog turned on ? >> I have a couple of other small fixes too. github is down right now, but I >> will push them as soon as I see it up. > > Great stuff. Looking forward to your fixes, github is back and they are at 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 -~----------~----~----~----~------~----~------~--~---
