[asterisk-bugs] [JIRA] (ASTERISK-26505) Using res_odbc module for querying a longBLOB column determine a big memory leak
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed Oct 26 11:26:01 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232865#comment-232865 ]
Asterisk Team commented on ASTERISK-26505:
------------------------------------------
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
> Using res_odbc module for querying a longBLOB column determine a big memory leak
> --------------------------------------------------------------------------------
>
> Key: ASTERISK-26505
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26505
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_odbc
> Affects Versions: 13.2.0, 13.4.0, 13.11.2
> Environment: CentOS 6.x 64 bit, Mysql 5.1
> Reporter: Leandro Dardini
> Severity: Minor
>
> Please note I have listed the versions where I tried this. Not listed version were not tested.
> If I have a table with a longBLOB field (but probably it happens for any type of BLOB column) and I define in func_odbc.conf an entry like
> [READ_EXTENSIONS]
> dsn=asterisk1,asterisk2
> synopsis=Retrieve the extension data
> readsql=SELECT * FROM ex_extensions where id='${ARG1}'
> Using a function like
> Set(HASH(phone)=${ODBC_READ_EXTENSIONS(56)});
> The same command, using any other type of column, gives no problems at all.
> Determines an increase of virtual memory usage in Asterisk... I have seen it getting up to 30 GB on a medium sized server.
> When this abnormal memory usage happens, asterisk continue to work, but it cannot spawn external processes, like from res_agi.c:
> [2016-10-26 10:04:18] WARNING[26880][C-000002bb] res_agi.c: Failed to fork(): Cannot allocate memory
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list