I'm running the service under valgrind again, and am not seeing that leak anymore:
==20111== LEAK SUMMARY: ==20111== definitely lost: 0 (+0) bytes in 0 (+0) blocks ==20111== indirectly lost: 0 (+0) bytes in 0 (+0) blocks ==20111== possibly lost: 10,100 (-88) bytes in 158 (-2) blocks ==20111== still reachable: 238,449 (-6,235) bytes in 3,996 (-38) blocks ==20111== suppressed: 0 (+0) bytes in 0 (+0) blocks
I'll let it continue for a couple of hours to make sure it's gone.
I'm running the service under valgrind again, and am not seeing that leak anymore:
==20111== LEAK SUMMARY:
==20111== definitely lost: 0 (+0) bytes in 0 (+0) blocks
==20111== indirectly lost: 0 (+0) bytes in 0 (+0) blocks
==20111== possibly lost: 10,100 (-88) bytes in 158 (-2) blocks
==20111== still reachable: 238,449 (-6,235) bytes in 3,996 (-38) blocks
==20111== suppressed: 0 (+0) bytes in 0 (+0) blocks
I'll let it continue for a couple of hours to make sure it's gone.