[Serdev] [Tracker] Created: (SER-220) False critical error: memory leak detected

[Michal Matyska (JIRA)]

False critical error: memory leak detected
------------------------------------------

                 Key: SER-220
                 URL: http://tracker.iptel.org/browse/SER-220
             Project: SER
          Issue Type: Bug
          Components: core
    Affects Versions: Ottendorf
         Environment: CVS head
            Reporter: Michal Matyska
            Priority: Minor


when processing requests you'll get following text in the syslog / stderr output:
Jan 31 17:59:08 xxx ser[24815]: CRITICAL: possible memory leak detected: free mem before/after script: 3290060/3290028
Jan 31 17:59:08 xxx ser[24815]: CRITICAL: possible memory leak detected: used mem before/after script: 479280/479360
Jan 31 17:59:08 xxx ser[24815]: CRITICAL: possible memory leak detected: real used mem before/after script: 904244/904276

It can be false alarm in following cases:
- qm manager was compiled without QM_JOIN_FREE and the list of fragments needed to allocate memory block for its own purpose
- select framework needed to allocate bigger memory block for its "static buffer"


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira