[OpenSER-Devel] Memory Leak?
miconda at gmail.com
Fri Jul 18 15:47:49 CEST 2008
On 07/18/08 16:05, Andrew O. Zhukov wrote:
> Daniel-Constantin Mierla пишет:
>> On 07/18/08 15:17, Dan Pascu wrote:
>>> It's more likely that this is not a memory leak, but a memory
>>> fragmentation issue. If you happen to run a fifo command like
>>> ul_dump with a lot of active contacts, it'll allocate a lot of small
>>> fragments and the memory gets fragmented. Later even after the
>>> memory is freed, it will not be able to allocate a 500+ byte memory
>>> block because the memory is too fragmented and memory allocation
>>> will fail even when 90% of the pkg_memory is free.
>> Could be fragmentation, but that has to happen due to operations in
>> that process. What is done via fifo affects only the memory of fifo
>> listener process. In SIP workers process can be due to lot of SIP
>> messages processing -- parsing, script variables, db operations,...
>> Compile with memory debug and see the log dump, that will give more
> Let me know if you need something else, like a sip_trace table
> extractions, openser.ini, etc..
I need the log from openser compiled with memory debugging on -- see the
link I sent. Looks as being some leak there, those logs show from where
the chinks are allocate.
More information about the Devel