[asterisk-bugs] [JIRA] (ASTERISK-18867) Incorrect Password in jabber.conf leads to memory leak

[Malcolm Davenport (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-18867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Malcolm Davenport closed ASTERISK-18867.
----------------------------------------

    Resolution: Fixed

By the looks of it, the original issue was reported fixed.

> Incorrect Password in jabber.conf leads to memory leak
> ------------------------------------------------------
>
>                 Key: ASTERISK-18867
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18867
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_jabber
>    Affects Versions: 1.8.6.0
>         Environment: Ubuntu 11.04 x64
>            Reporter: Nigel Vander Houwen
>            Assignee: Dave Bowerman
>         Attachments: Asterisk_Mem_Data.txt, issueA18867-jabber_missing_unref.patch, jabber-authfail.patch
>
>
> I have my asterisk setup configured for calling via Google Voice as per the directions here: https://wiki.asterisk.org/wiki/display/AST/Calling+using+Google
> I recently updated my google password, and forgot to update the password in jabber.conf for the asterisk server. I don't do a lot of calling, so I didn't really notice it for a while. Anyway, the server crashed, I thought it was a fluke, restarted it, and then looked again today and RAM was totally used up and swap was getting close. TOP indicated asterisk as the culprit. Logged into the CLI with high verbosity, and it was spewing constant errors about the password (Sorry, I didn't grab a copy of one of the lines before I fixed it). Anyway, I corrected the password and restarted asterisk and things seem happy again.
> I don't assume that complete ram usage and server crashing is defined behavior for an incorrect password.



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