In the last episode (Sep 27), Per Hedbor () @ Pike (-) developers forum said:
Nothing that can be easily detected as anything 'non-normal' in the memory. No large heaps of SQL queries or replies as far as I can see.
Nor any other easily detectable strings in the 1000 different positions I tried.
How about building pike --with-dmalloc? Although that doesn't look like it actually uses dmalloc; it's more of an internal malloc tracer for pike internals.
Or, try installing dmalloc, export LD_PRELOAD=/usr/local/lib/libdmalloc.so, run this to enable leak checking:
eval `dmalloc -b -l /tmp/dmalloc.log -p log-non-free`
then start roxen. If you do a clean shutdown, you should then end up with a list of all leaked memory in /tmp/dmalloc.log. When dmalloc is preloaded like that instead of compiled in, you only get hex addresses instead of function names, but if you run "gcore" to generate a coredump of the pike process just before you shutdown, you can load that info gdb and run "info line *(0x280579fe)" to get the function corresponding to ra=0x280579fe, for example.