| Summary: | ASTERISK-12207: Memory Leak in HTTP Manager Interface | ||
| Reporter: | Ken Leland (kenlee) | Labels: | |
| Date Opened: | 2008-06-16 13:19:35 | Date Closed: | 2008-06-17 10:51:09 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/HTTP |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) http-login_query_logoff.cpt | |
| Description: | There is a memory leak in the code relating to http manager session management. ****** ADDITIONAL INFORMATION ****** I am logging in and out of the HTTP Manager Interface approximately once per second (from a script). This is exercising a leak that is causing the available system memory to decrease to zero in a matter of several days at which point Asterisk crashes. I can avoid the crash by restarting Asterisk often enough. While logging in and out verbose console output shows: == Parsing '/etc/asterisk/manager.conf': Found == HTTP Manager 'guest' logged on from 200.255.100.3 == HTTP Manager 'guest' logged off from 200.255.100.3 | ||
| Comments: | By: Ken Leland (kenlee) 2008-06-16 13:22:33 Why is 'manager.conf' parsed on every log in? By: Ken Leland (kenlee) 2008-06-16 15:33:35 I have attached a packet capture of the interaction between my script and the Asterisk HTTP Manager Interface. Here is a summary of the script's three requests which when repeated exercise the memory leak: GET /asterisk/manager?action=login&username=guest&secret=read*only GET /asterisk/mxml?action=queuestatus GET /asterisk/mxml?action=logoff By: Russell Bryant (russell) 2008-06-17 10:51:07 should be fixed in revs 123271, 123272, and 123273. | ||