[asterisk-bugs] [JIRA] (ASTERISK-17752) (not so)large astDB key values cause asterisk to take up a lot of memory

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-17752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225405#comment-225405 ] 

Matt Jordan commented on ASTERISK-17752:
----------------------------------------

And, still not a bug :-)

I was able to reproduce this using Asterisk 11 and with Verbosity enabled going to the CLI. Memory usage in Asterisk kept increasing as the channel spammed itself. However, upon some additional investigation, this was due to log messages showing the infinite loop executing getting queued up and dispatched to the CLI.

Running Asterisk without verbosity results in no memory increasing for the process, even as the channel spams the AstDB and pegs a CPU. But again, the channel is in an infinite loop, so that's expected.

> (not so)large astDB key values cause asterisk to take up a lot of memory
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-17752
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17752
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Applications/app_db
>    Affects Versions: 1.8.3
>            Reporter: Jacco van Tuijl
>            Severity: Minor
>
> I've been testing astDB limits in combination with asterisk.
> a simple dialplan :
> {noformat}
> exten = _X.,n(waiting),Set(DB(test/testing)=${DB(test/testing)}a)
> exten = _X.,n,goto(waiting)
> {noformat}
> made the value length grow up to max. 4096bytes causing asterisk to take up 84% memory on a machine with 4gb ram
> also in one of the test a whitespace came out of nowhere:
> http://pastebin.com/gpbpcjzR



--
This message was sent by Atlassian JIRA
(v6.2#6252)