|
From: | Kenneth Loafman |
Subject: | Re: [Duplicity-talk] apparent memory leak on OS X |
Date: | Mon, 9 Jan 2012 09:16:20 -0600 |
On 6 January 2012 19:45, Nate Eldredge <address@hidden> wrote:Ah, that's me! :) Thanks for tracking it down that far.
> To further narrow this down, I tried some different revisions in the
> lp:duplicity branch. It appears that revision 782 is good but 783 has the
> bug. The relevant change is labeled
>
> "Merged in lp:~mterry/duplicity/tarfile"
Unfortunately, that was a rather big merge.
I'm happy to look into this, but I don't have much experience with
debugging leaks in Python. Are there good tools or techniques for
that?
[Prev in Thread] | Current Thread | [Next in Thread] |