On Nov 26, 11:53 pm, Andreas Fuchs <[EMAIL PROTECTED]> wrote: > > Someone who sees this problem: can you give more details of which > > version of Mac OS and libevent you're using? Are you running 64-bit? > > Is anyone willing to run beanstalkd under valgrind (either memcheck or > > massif)? That would be incredibly helpful, since I'm so far unable to > > reproduce it. [...] > 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.
Well, ha ha. Valgrind is not entirely ported to OS X, and the beta patch for running on OS X (at http://www.sealiesoftware.com/valgrind/) makes it crash when invoked with beanstalkd. )-: I tried running with MallocStackLogging=1 (to run with leaks(1)), and that reports: $ ps aux | grep [b]eanstalkd asf 31582 0.0 9.4 993380 197188 ?? Ss 8:39PM 0:00.33 ./beanstalkd $ leaks beanstalkd Process 31582: 42 nodes malloced for 393620 KB Process 31582: 0 leaks for 0 total leaked bytes. Well, erm. What? Also, I slowed things down a bit, and it looks like memory usage doubles every time a request is enqueued. This doesn't appear to affect /all/ requests, though. Any other insights or debugging aids on OS X that could help? Cheers, Andreas. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
