Henning Westerholt пишет:
> On Friday 18 July 2008, Andrew O. Zhukov wrote:
>> This openser compiled exactly as in your link:
>>
>> What's wrong?
>> -DSTATISTICS \
>> -DCHANGEABLE_DEBUG_LEVEL \
>> #-DF_MALLOC \
>> -DDBG_QM_MALLOC \
>
> Hi Andrew,
>
> i reme
On 07/18/08 17:03, Andrew O. Zhukov wrote:
> Daniel-Constantin Mierla пишет:
>
>> 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
On Friday 18 July 2008, Andrew O. Zhukov wrote:
> This openser compiled exactly as in your link:
>
> What's wrong?
> -DSTATISTICS \
> -DCHANGEABLE_DEBUG_LEVEL \
> #-DF_MALLOC \
> -DDBG_QM_MALLOC \
Hi Andrew,
i remember some issues with make if you have a co
Daniel-Constantin Mierla пишет:
>
>
> 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 lik
On 07/18/08 15:48, Andrew O. Zhukov wrote:
>>
>> Compile with memory debug and see the log dump, that will give more
>> hints:
>> http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory
>
> Sent directly to Daniel.
updating the list -- indeed seems like a leak, over 6k chunks in may
pro
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
Bugs item #1967114, was opened at 2008-05-19 14:13
Message generated for change (Comment added) made by carstenbock
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1967114&group_id=139143
Please note that this message will contain a full copy of the comme
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 t
>
> Compile with memory debug and see the log dump, that will give more hints:
> http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory
Sent directly to Daniel.
>
>
> Daniel
>> On Friday 18 July 2008, Andrew O. Zhukov wrote:
>>
>>> What should I do to catch?
>>>
>>> happends 2-d tim
Thanks Dan,
Actually i have not more then 100 active registration yet...
The question is how to fix?
So, I save a memory debug log from this issue. Is it helpful for you?
I can send it directly.
Dan Pascu пишет:
> It's more likely that this is not a memory leak, but a memory
> fragmentation i
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 afte
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 t
What should I do to catch?
happends 2-d time for the last 2 monthes?
After this all INVITE-s crashed with memory allocation errors.
switch on
define #XL_DEBUG?
other suggestions?
Jul 17 15:13:18 ipshka openser[26649]: Request leaving server - M=INVITE
RURI=sip:[EMAIL PROTECTED]:5060
F=sip:[E
Ready to provide complete log file with memory debug on directly to
developers.
Henning Westerholt пишет:
> On Wednesday 09 July 2008, Andrew O. Zhukov wrote:
>> [..]
>
> Hi Andrew,
>
> i think i've found some problems in the postgres module. The problem were
> caused from a invalid data in th
14 matches
Mail list logo
