Author pablogsal
Recipients Mark.Shannon, christian.heimes, jdemeyer, lukasz.langa, pablogsal, petr.viktorin, pitrou, vstinner
Date 2019-09-02.15:44:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1567439042.4.0.958395711969.issue38006@roundup.psfhosted.org>
In-reply-to
Content
Unless we are missing something I think this may be caused by something in cffi that is not implementing gc-related functions correctly, as PyObject_ClearWeakRefs should not be called from a gc run. Given how complicated this is and even if the possible solution is to fix the problem in cffi or elsewhere, we can add an extra check in PyObject_ClearWeakRefs to NOT call callbacks that are in the process of being collected. Technically we should never reach that code, but we won't be segfaulting and the cost is a redundant-check that will be false in the normal path.
History
Date User Action Args
2019-09-02 15:44:02pablogsalsetrecipients: + pablogsal, pitrou, vstinner, christian.heimes, petr.viktorin, lukasz.langa, Mark.Shannon, jdemeyer
2019-09-02 15:44:02pablogsalsetmessageid: <1567439042.4.0.958395711969.issue38006@roundup.psfhosted.org>
2019-09-02 15:44:02pablogsallinkissue38006 messages
2019-09-02 15:44:01pablogsalcreate