[asterisk-bugs] [JIRA] (ASTERISK-20649) valgrind reports memory leaks
Corey Farrell (JIRA)
noreply at issues.asterisk.org
Mon Nov 5 17:55:21 CST 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199266#comment-199266 ]
Corey Farrell commented on ASTERISK-20649:
------------------------------------------
Replacement patches coming shortly to fix naming issues with new procedures.
> valgrind reports memory leaks
> -----------------------------
>
> Key: ASTERISK-20649
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20649
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/General
> Affects Versions: 1.8.17.0
> Reporter: Corey Farrell
> Severity: Minor
> Attachments: ccss-cleanup.patch, cdr-cleanup.patch, cli-leaks.patch, config-cleanup.patch, core-cleanup.patch, db-cleanup.patch, dnsmgr-cleanup.patch, indications-cleanup.patch, logger-cleanup.patch, pbx-cleanup.patch, ssl-cleanup.patch, unregister-cli-multiple.patch
>
>
> Valgrind reports memory still allocated at exit. Patches will follow to address many of these issues against branch 1.8.
> ||Source||Issues||
> |many|CLI commands not unregistered|
> |ccss.c|Logger level not unregistered|
> |cdr.c|No cleanup at exit|
> |cli.c|Command registration leaks memory on some error's|
> |config.c|Config cache not cleared|
> |db.c|No cleanup at exit|
> |dnsmgr.c|No cleanup at exit|
> |indications.c|Sounds leaked when removed from zone
> Ringcadence allocated twice causing leak
> Shutdown incomplete|
> |logger.c|close_logger incomplete|
> |pbx.c|device_state_tps, hints and statecbs keep references|
> |ssl.c|No cleanup at exit|
> |asterisk.c|ast_run_atexits doesn't cleanup atexits list
> Shutdown from cli causes ast_cli_entry to be inuse
> Verbose runs ast_active_channels() after channels_shutdown|
> |stdtime/localtime.c|No cleanup. Cleanup needs to be done after logger cleanup|
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list