| Summary: | ASTERISK-13062: [patch] Memory leak if the sla_thread is not running | ||
| Reporter: | Eliel Sardanons (eliel) | Labels: | |
| Date Opened: | 2008-11-12 11:47:30.000-0600 | Date Closed: | 2008-11-12 13:26:41.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_meetme |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) app_meetme.c.patch | |
| Description: | If the sla_thread is not running, we are queueing events and we don't have a consumer. One of the leaks is generated when doing a 'module reload', it is queueing a RELOAD event, and no one is freeing it, because the thread is not running. The solution I present here is to avoid queueing an event if we have no thread assigned to consume this events. | ||
| Comments: | By: Digium Subversion (svnbot) 2008-11-12 13:26:40.000-0600 Repository: asterisk Revision: 156294 U branches/1.4/apps/app_meetme.c ------------------------------------------------------------------------ r156294 | tilghman | 2008-11-12 13:26:40 -0600 (Wed, 12 Nov 2008) | 6 lines If the SLA thread is not started, then reload causes a memory leak. (closes issue ASTERISK-13062) Reported by: eliel Patches: app_meetme.c.patch uploaded by eliel (license 64) ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=156294 | ||