Message 169934 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	pitrou
Recipients	alexandre.vassalotti, asvetlov, mstefanro, pitrou
Date	2012年09月06日.18:07:01
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1346954822.96.0.22111654626.issue15642@psf.upfronthosting.co.za>

Content
> Are there also some known techniques on tracking down memory leaks? Nothing more than the usual debugging techniques. It is more of a matter of taste whether you like to add print() (or printf ;-)) calls, or set breakpoints in an actual debugger. > i.e. pickle.dumps(3.0+1j, 4) leaks but pickle.dumps(3.0+1j, 3) does not. Well it looks like you've narrowed things down a bit here. > However, there appears to be no difference in the code that gets > executed in v3 to the one executed in v4. Even the differences in memoization?

Content

> Are there also some known techniques on tracking down memory leaks?
Nothing more than the usual debugging techniques. It is more of a matter of taste whether you like to add print() (or printf ;-)) calls, or set breakpoints in an actual debugger.
> i.e. pickle.dumps(3.0+1j, 4) leaks but pickle.dumps(3.0+1j, 3) does
not.
Well it looks like you've narrowed things down a bit here.
> However, there appears to be no difference in the code that gets
> executed in v3 to the one executed in v4.
Even the differences in memoization?

History
Date	User	Action	Args
2012年09月06日 18:07:03	pitrou	set	recipients: + pitrou, alexandre.vassalotti, asvetlov, mstefanro
2012年09月06日 18:07:02	pitrou	set	messageid: <1346954822.96.0.22111654626.issue15642@psf.upfronthosting.co.za>
2012年09月06日 18:07:02	pitrou	link	issue15642 messages
2012年09月06日 18:07:01	pitrou	create

homepage