Message 317498 - 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	methane
Recipients	asvetlov, methane, thehesiod, vstinner
Date	2018年05月24日.01:47:03
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1527126423.9.0.682650639539.issue33565@psf.upfronthosting.co.za>

Content
> The callstack I initially mentioned still has no explanation and we now know is not correct. I don't think so. The callstack is Python's callstack where caused leak in C. (Python doesn't call malloc directly) In this case, local variables are freed "at end of the function", and it freed unclosed socket which cause warning. () So the callstack is completely valid. While only CPython expert can understand. () or "at the end of the except clause" which frees `e` and `e` have reference to the unclosed socket.

Content

> The callstack I initially mentioned still has no explanation and we now know is not correct.
I don't think so.
The callstack is Python's callstack where caused leak in C. (Python doesn't call malloc directly)
In this case, local variables are freed "at end of the function", and it freed unclosed socket which cause warning. (*)
So the callstack is completely valid. While only CPython expert can understand.
(*) or "at the end of the except clause" which frees `e` and `e` have reference to the unclosed socket.

History
Date	User	Action	Args
2018年05月24日 01:47:03	methane	set	recipients: + methane, vstinner, asvetlov, thehesiod
2018年05月24日 01:47:03	methane	set	messageid: <1527126423.9.0.682650639539.issue33565@psf.upfronthosting.co.za>
2018年05月24日 01:47:03	methane	link	issue33565 messages
2018年05月24日 01:47:03	methane	create

homepage