Comment 28 for bug 1203276

After 5 minutes:

==24889== HEAP SUMMARY:
==24889== in use at exit: 590,596 bytes in 2,104 blocks
==24889== total heap usage: 328,916 allocs, 326,812 frees, 31,643,363 bytes allocated

==24889== LEAK SUMMARY:
==24889== definitely lost: 345 bytes in 345 blocks
==24889== indirectly lost: 0 bytes in 0 blocks
==24889== possibly lost: 3,936 bytes in 10 blocks
==24889== still reachable: 586,315 bytes in 1,749 blocks

After 17 hours:

==24934== HEAP SUMMARY:
==24934== in use at exit: 654,785 bytes in 66,205 blocks
==24934== total heap usage: 52,150,395 allocs, 52,084,190 frees, 4,955,956,671 bytes allocated

==24934== LEAK SUMMARY:
==24934== definitely lost: 64,446 bytes in 64,446 blocks
==24934== indirectly lost: 0 bytes in 0 blocks
==24934== possibly lost: 3,936 bytes in 10 blocks
==24934== still reachable: 586,403 bytes in 1,749 blocks

Correct me if I'm wrong but as I understand it:
It uses 586Kb regardless how long it runs.
Yes it still leaks, I've known that but have not been able to fix the last bit.
But on my machine it leaks 64Kb in 17h -> 4Kb/h

Run 'valgrind --leak-check=full /usr/sbin/cups-browsed' on your machine and if you have significantly different numbers, attach the output here. Thanks