[asterisk-bugs] [JIRA] (ASTERISK-26171) REF_DEBUG: support writing storage address to refs log.

Corey Farrell (JIRA) noreply at issues.asterisk.org
Sat Jul 2 15:18:56 CDT 2016


     [ https://issues.asterisk.org/jira/browse/ASTERISK-26171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell updated ASTERISK-26171:
-------------------------------------

    Reviewboard Link: https://gerrit.asterisk.org/3141

> REF_DEBUG: support writing storage address to refs log.
> -------------------------------------------------------
>
>                 Key: ASTERISK-26171
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26171
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/AstMM
>    Affects Versions: SVN
>            Reporter: Corey Farrell
>            Assignee: Corey Farrell
>            Severity: Minor
>         Attachments: refs-filter-matched.txt, refs-unfiltered.txt
>
>
> The ability to associate an AO2 reference with a pointer will allow {{refcounter.py}} to greatly reduce the output for leaked objects.  The use of ast_format in frame.c is a perfect example.  The same format is often used thousands of times but frame.c is rarely the cause of a format leaking.  This change causes matching ref/unref from frame.c and a few other places to be filtered out of the results.  This is done by associating references with address of the pointer that will hold it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list