Carlos R. Mafra wrote: > On Mon 17.Aug'09 at 15:10:00 +0200, Carlos R. Mafra wrote: > > Is is possible to track down where this memory increase is coming > > from and whether it is expected or not? > > Someone suggested to me off-list to use valgrind. This is the > summary of my first test a few hours ago: > > LEAK SUMMARY: > ==26635== definitely lost: 3,618 bytes in 12 blocks. > ==26635== indirectly lost: 5,312 bytes in 166 blocks. > ==26635== possibly lost: 0 bytes in 0 blocks. > ==26635== still reachable: 1,571,268 bytes in 13,554 blocks. > ==26635== suppressed: 0 bytes in 0 blocks. > ==26635== Reachable blocks (those to which a pointer was found) are not shown. > ==26635== To see them, rerun with: --leak-check=full --show-reachable=yes > > So yeah, it looks like there a few memory leaks in wmaker.
I'm not surprised. It will take a while to hunt them all down and plug them up. -- John H. Robinson, IV [email protected] http (((( WARNING: I cannot be held responsible for the above, sbih.org ( )(:[ as apparently my cats have learned how to type. spiders.html (((( -- To unsubscribe, send mail to [email protected].
