➜

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.

Author vstinner
Recipients jdemeyer, pablogsal, serhiy.storchaka, vstinner
Date 2018-07-23.13:42:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532353338.48.0.56676864532.issue34190@psf.upfronthosting.co.za>
In-reply-to
Content 
Ok, so it's a real bug, a reference leak, which have been introduced by:

commit 93fac8dd358cd0e85e7b59115db226ce685d3f6f
Author: INADA Naoki <methane@users.noreply.github.com>
Date:   Tue Mar 7 14:24:37 2017 +0900

    bpo-29676: fix lsprof can't profile C method call. (GH523)
    
    When LOAD_METHOD is used for calling C mehtod, PyMethodDescrObject
    was passed to profilefunc from 5566bbb.
    But lsprof traces only PyCFunctionObject. Additionally, there can be
    some third party extension which assumes passed arg is
    PyCFunctionObject without calling PyCFunction_Check().
    
    So make PyCFunctionObject from PyMethodDescrObject when
    tstate->c_profilefunc is set.
History
Date User Action Args
2018-07-23 13:42:18vstinnersetrecipients: + vstinner, serhiy.storchaka, jdemeyer, pablogsal
2018-07-23 13:42:18vstinnersetmessageid: <1532353338.48.0.56676864532.issue34190@psf.upfronthosting.co.za>
2018-07-23 13:42:18vstinnerlinkissue34190 messages
2018-07-23 13:42:18vstinnercreate