| Summary: | ASTERISK-05845: Cummulative memory consumption using applications ODBC or MYSQL | ||
| Reporter: | Jon Brüel (jb) | Labels: | |
| Date Opened: | 2005-12-15 04:29:35.000-0600 | Date Closed: | 2005-12-17 10:08:10.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) dialplan2.txt | |
| Description: | This applies for version 1.1.10 as well as 1.2.1, both stable. The problem has existed on many of the Asterisk. In version 1.0.10, the memory consumption increases by around 13 MB when 1000 ODBC reads or inserts are made, using the application ODBCget og ODBCput. In version 1.2.1, the memory consumption increases by around 2 MB when 1000 ODBC reads or inserts are med, using the application MYSQL. The effect of this memomy consumption is that Asterisk runs out of memory during the day in situations with more than 2000 call attempts to the extensions an hour. Memory is freed after a restart of Asterisk. ****** ADDITIONAL INFORMATION ****** MySQL version: 3.23.58 Linux version: FC 2. Servertype: i686 The dialplan, rather complex, for Asterisk versin 1.0.10, is attached as a word-file. Naturally, it would be best, if these database calls did not take up the memrory consumption. But a possible fix could be to make regular "restart when convenient" triggered by memory usage over a defined limit. Such a command could also be triggered by other factors, and could be used as a general watchdog function. | ||
| Comments: | By: Tilghman Lesher (tilghman) 2005-12-17 09:55:58.000-0600 1) ODBCput/ODBCget are not part of Asterisk. 2) The MYSQL app is only part of the addons, and is thus not maintained except by the authors of that module. 3) I would highly recommend that you use the code in bug ASTERISK-4925 going forward, as this is likely to become part of Asterisk in the future (probably in 1.4). | ||