Anonymous | Login | Signup for a new account | 2022-08-19 13:46 EEST |
Main | My View | View Issues | Change Log | Roadmap | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0000439 | [Yate - Yet Another Telephony Engine] engine | major | always | 2021-04-06 11:11 | 2021-04-21 21:17 | ||||
Reporter | ServeyV | View Status | public | ||||||
Assigned To | marian | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | resolved | Product Version | SVN | ||||||
Summary | 0000439: Memory/mutex leak on SIP REFER | ||||||||
Description |
Problem exists in 6.1 and 6.3 As I understand, after each REFER one mutex not destroyed and as result we have 587131 mutexes and 2.6Gb memory usage: name=engine,type=system,version=6.1.0,revision=6319,nodename=xxx;plugins=63,inuse=2,handlers=428,hooks=3,messages=0,maxqueue=16,messageage=1,messagerate=32,maxmsgrate=421,enqueued=28640288,dequeued=28640288,dispatched=40310927,supervised=true,runattempt=1,lastsignal=0,threads=243,workers=2,mutexes=587131,semaphores=0,acceptcalls=accept,congestion=0;sharedpath=/usr/local/share/yate,configpath=/usr/local/etc/yate,usercfgpath=/root/.yate,modulepath=/usr/local/lib/yate,workpath=/root Scenarion: 1. Call from client to yate to 123 2. Yate route call to 234 on server 3. Server send REFER to 345 to Yate 4. Yate reroute call to 456 to the same server 5. Terminate call on client All legs terminated w/o errors, but after each test mutexes increased by one |
||||||||
Additional Information | |||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
|
Copyright © 2000 - 2008 Mantis Group |