[asterisk-dev] [Code Review] 4141: Enable REF_DEBUG for ast_module_ref / ast_module_unref

Corey Farrell reviewboard at asterisk.org
Wed Feb 11 09:38:49 CST 2015

This is an automatically generated e-mail. To reply, visit:

(Updated Feb. 11, 2015, 9:38 a.m.)


This change has been marked as submitted.

Review request for Asterisk Developers.


Committed in revision 431662

Bugs: ASTERISK-24479

Repository: Asterisk


This change includes an ABI change with compatibility stubs for 11 and 13.  The compatibility stubs will not be included in trunk.  The point of this change is to have each module create an AO2 object on load, and hopefully destroy it on unload.  This allows module reference count errors to be debugged through REF_DEBUG.

When REF_DEBUG is enabled:
* adds an empty ao2 object to 'struct ast_module'
* Allocate ao2 when the module is loaded
* Perform an ao2_ref in each place where mod->usecount is manipulated.
* ao2_cleanup on module unload.

The passthrough of file, line and func is needed for the REF_DEBUG to be of any use, so without the ABI changes this is not useful.

The change to bridge_builtin_features.c ensures that the module cannot be manually unloaded, but is able to be unloaded during ast_module_shutdown.  Note ast_module_shutdown only happens during clean shutdown and does not actually run dlclose so this is safe.


  /branches/11/main/loader.c 429406 
  /branches/11/include/asterisk/module.h 429406 
  /branches/11/bridges/bridge_builtin_features.c 429406 

Diff: https://reviewboard.asterisk.org/r/4141/diff/


Using tests/manager/originate with REF_DEBUG enabled.  When the change to bridge_builtin_features.c is omitted the test fails due to that one reference leak.


Corey Farrell

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20150211/c27da35e/attachment.html>

More information about the asterisk-dev mailing list