Hi Steve, On Wed, Nov 29, 2017 at 11:13:34AM +0000, Steve Kemp wrote: > > Description : debug a running process for memoy leaks without > > recompiling or restarting > > Typo: "memory", not "memoy". [...] > > Differences from Valgrind: > > . > > * Valgrind starts the target process, while memleax attaches to on that is > > already running. > > Nor this.
Thank you for the edits and suggestions. I've also shortened the short description by dropping 'without recompiling or restarting', and have updated to the newest upstream version (1.1.0). Unfortunately my first attempt at using memleax failed. The first run produced more output than expected, and I thought I'd try to set a longer period than 10 seconds to gather more dramatic data (when redirecting output to a file). Unfortunately the process hung, presumably because /proc/pid/map disappeared. A third run confirmed that /proc/pid/map was gone and wouldn't come back. I'm trying to collect more data for #879901. When the bug reoccurred this month kded5 was holding onto 6520.81MB of RAM ! At any rate, would you like to comaintain or sponsor this package? The remote is here ssh://git.debian.org/git/collab-maint/memleax.git and I'd be happy to add you to uploaders before finalising the changelog and putting the package on mentors! Sincerely, Nicholas
signature.asc
Description: PGP signature
