Author ncoghlan
Recipients eric.snow, ncoghlan, paul.moore, pjna, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-11-15.06:27:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510727276.56.0.213398074469.issue32026@psf.upfronthosting.co.za>
In-reply-to
Content
I think it's reasonable to keep this open if the problems can be reproduced with the current 3.7 dev branch - while we've refactored a lot of things, we haven't specifically gone memory leak hunting for the embedded case, and I'm pretty sure there are still some items where we delay cleaning them up until the next Py_Initialize call.

The relevant embedding test case is the one at https://github.com/python/cpython/blob/master/Programs/_testembed.c#L41, but I'm not sure we regularly run that in a way that would reliably detect memory leaks (it runs in a subprocess, rather than the main process, so the refleak hunting runs may not be handling it properly).
History
Date User Action Args
2017-11-15 06:27:56ncoghlansetrecipients: + ncoghlan, paul.moore, vstinner, tim.golden, eric.snow, zach.ware, steve.dower, pjna
2017-11-15 06:27:56ncoghlansetmessageid: <1510727276.56.0.213398074469.issue32026@psf.upfronthosting.co.za>
2017-11-15 06:27:56ncoghlanlinkissue32026 messages
2017-11-15 06:27:56ncoghlancreate