I think I found my memleak
http://comments.gmane.org/gmane.network.zeromq.devel/10473
It turned out you need to provide a custom deallocator or the buffer
would remain. Will provide a fix.
On 07/19/2012 10:17 PM, Douglas Hubler wrote:
ah, 32bit, ultimately you'll hit
http://track.sipfoundry.org/browse/XX-10272
but you're not there yet.
I just discovered sipxsqa (Network Queue) has a significant memory
leak. I would suggest you wait just a couple more days to test
homer.
On Thu, Jul 19, 2012 at 10:08 AM, jnolen <[email protected]> wrote:
Douglas,
Restarts no help.
Get slightly different results on packages (32-bit system):
# rpm -qa | grep homer
sipxhomer-config-4.6.0-11.g161c.i686
sipxhomer-4.6.0-11.g161c.i686
homer-3.2.5-1.el6.i686
sipxhomer-proxyplugin-4.6.0-11.g161c.i686
On Thu, Jul 19, 2012 at 9:40 AM, jnolen <[email protected]> wrote:
"2012-07-19T12:30:50.313192Z":6:NET:ERR:sipx.domain.net:task-3031432048:b4affb70:sipxhomer:"StateQueueClient::eventLoop
Is unable to
SIGN IN to SQA service"
Try restarting, might be race condition. Also, double check update ver
yum -qa | grep homer
should be:
sipxhomer-config-4.6.0-11.g161c.x86_64
sipxhomer-proxyplugin-4.6.0-11.g161c.x86_64
homer-3.2.5-1.el6.x86_64
sipxhomer-4.6.0-11.g161c.x86_64
NOTE: Restarting sipxhomer and sipxsqa. Restarted is done w/CLI w/traditional
/etc/init.d/sipxhomer restart
/etc/init.d/sipxsqa restart
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
