Hi Tshepang, On Wed, 2010-01-20 at 17:06 +0200, Tshepang Lekhonkhobe wrote: > the summary looks strange, especially since valgrind was eating 1.1GB of RAM > > ==25394== LEAK SUMMARY: > ==25394== definitely lost: 344 bytes in 25 blocks > ==25394== indirectly lost: 120 bytes in 10 blocks > ==25394== possibly lost: 17,783 bytes in 209 blocks > ==25394== still reachable: 67,335 bytes in 1,419 blocks > ==25394== suppressed: 4,952 bytes in 121 blocks
I've just pushed a commit that significantly reduces memory used for event handling. It's possible that you weren't seeing leaks, just excessive temporary memory usage. That would explain the above valgrind summary. If you've still been seeing the high memory usage with recent versions, please let me know if current master improves the situation. Thanks, Jürg _______________________________________________ tracker-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/tracker-list
