Hi Hanh,

That's good news. As it seemed strange no one else would have picked up this
issue for smsbox, which is so well used.

However for opensmppbox, which is not as well used as smsbox, there may
still be actual memory leaks.
Please check again using your new virtual machine and send us your results
using: 
valgrind --leak-check=full --track-origins=yes ./opensmppbox

thanks

----------------------------------------------------------------------
Date: Sat, 7 Jun 2014 10:31:18 +0700
From: Hanh Le Bich <hanhmi...@gmail.com>
To: Stipe Tolj <st...@kannel.org>
Cc: devel@kannel.org
Subject: Re: Does opensmppbox and smsbox have serious memory issues?
Message-ID:
        <ca+p4dgyjy-26_t0rhpkohrmtqebavk8gceqslkh6jvvbbpy...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi Stipe and list,
I don't know how to say now. I had migrated my SMS Broadcast system to
another server last week (an Virtual machine) and there is no mem leak of
smsbox  any more.
I've tested for every scenarios and it is clean:

==22709== Memcheck, a memory error detector ==22709== Copyright (C)
2002-2013, and GNU GPL'd, by Julian Seward et al.
==22709== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info
==22709== Command: /usr/local/sbin/smsbox -v -d -- /etc/kannel/kannel.conf
==22709== Parent PID: 22707 ==22709== ==22709== ==22709== HEAP SUMMARY:
==22709==     in use at exit: 2,184 bytes in 39 blocks
==22709==   total heap usage: 3,084,394 allocs, 3,084,355 frees,
630,991,485 bytes allocated
==22709==
==22709== LEAK SUMMARY:
==22709==    definitely lost: 0 bytes in 0 blocks
==22709==    indirectly lost: 0 bytes in 0 blocks
==22709==      possibly lost: 0 bytes in 0 blocks
==22709==    still reachable: 2,184 bytes in 39 blocks
==22709==         suppressed: 0 bytes in 0 blocks
==22709== Reachable blocks (those to which a pointer was found) are not
shown.
==22709== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==22709== ==22709== For counts of detected and suppressed errors, rerun
with: -v ==22709== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6
from 4)

Suppose that i have physical mem issue in my old machine(!?), cause in
migration progress, i found the old one has an alarm at its booting time:
"8601: All memory marked as fail. Forcing minimum back online." Then i have
to press F1 to Resume.

I apology and appreciate all of you to spending time on this issue. If have
any request for testing in high loading, also  the opensmppbox mem leak,
please let me know. Thank you.

Regards,
Hanh.


On Mon, Jun 2, 2014 at 8:48 PM, Stipe Tolj <st...@kannel.org> wrote:

> Am 20.05.2014 04:54, schrieb Hanh Le Bich:
>
>  Hello again,
>> Sorry for late reply, i was stuck on field.
>>
>> 1. I upload again the previous Valgrind report in below link also in 
>> attachment as usual:
>> https://www.dropbox.com/s/wbnkewitosiwv5i/opensmppbox_
>> memleakcheck_20140502.txt
>>
>> 2. Here is my kannel configuration:
>> https://www.dropbox.com/s/u90vs8srbubbmhn/kannel_configuration_file.t
>> xt
>>
>
> Hi list,
>
> I can't reproduce the memory leak that Hanh is reporting here, even 
> with setting 'smsbox-id' in the 'group = smsbox' context I get clean 
> memory deallocations.
>
> Here is my valgrind report:
>
> ==00:00:00:00.000 14193== Memcheck, a memory error detector.
> ==00:00:00:00.000 14193== Copyright (C) 2002-2007, and GNU GPL'd, by 
> Julian Seward et al.
> ==00:00:00:00.000 14193== Using LibVEX rev 1854, a library for dynamic 
> binary translation.
> ==00:00:00:00.000 14193== Copyright (C) 2004-2007, and GNU GPL'd, by 
> OpenWorks LLP.
> ==00:00:00:00.000 14193== Using valgrind-3.3.1-Debian, a dynamic 
> binary instrumentation framework.
> ==00:00:00:00.000 14193== Copyright (C) 2000-2007, and GNU GPL'd, by 
> Julian Seward et al.
> ==00:00:00:00.000 14193== For more details, rerun with: -v
> ==00:00:00:00.000 14193==
> ==00:00:00:00.000 14193== My PID = 14193, parent PID = 1.  Prog and 
> args
> are:
> ==00:00:00:00.000 14193== /home/tolj/src/kannel/devel/ 
> gateway-redis/gw/smsbox
> ==00:00:00:00.000 14193==    -v
> ==00:00:00:00.000 14193==    4
> ==00:00:00:00.000 14193==    -p
> ==00:00:00:00.000 14193==    /opt/kannel/var/run/smsbox_client.pid
> ==00:00:00:00.000 14193==    /opt/kannel/etc/kannel_client.conf
> ==00:00:00:00.000 14193==
> ==00:00:05:18.814 14193==
> ==00:00:05:18.814 14193== FILE DESCRIPTORS: 6 open at exit.
> ==00:00:05:18.814 14193== Open file descriptor 6:
> ==00:00:05:18.814 14193==    at 0x71E2377: pipe (in /usr/lib/debug/
> libc-2.7.so)
> ==00:00:05:18.814 14193==    by 0x437A2E: fill_threadinfo
> (gwthread-pthread.c:186)
> ==00:00:05:18.814 14193==    by 0x437D0D: gwthread_init
> (gwthread-pthread.c:281)
> ==00:00:05:18.814 14193==    by 0x4371D9: gwlib_init (gwlib.c:85)
> ==00:00:05:18.814 14193==    by 0x40FC5C: main (smsbox.c:3543)
> ==00:00:05:18.814 14193==
> ==00:00:05:18.814 14193== Open file descriptor 5:
> ==00:00:05:18.814 14193==    at 0x71E2377: pipe (in /usr/lib/debug/
> libc-2.7.so)
> ==00:00:05:18.814 14193==    by 0x437A2E: fill_threadinfo
> (gwthread-pthread.c:186)
> ==00:00:05:18.814 14193==    by 0x437D0D: gwthread_init
> (gwthread-pthread.c:281)
> ==00:00:05:18.814 14193==    by 0x4371D9: gwlib_init (gwlib.c:85)
> ==00:00:05:18.814 14193==    by 0x40FC5C: main (smsbox.c:3543)
> ==00:00:05:18.814 14193==
> ==00:00:05:18.814 14193== Open file descriptor 3:
> /opt/kannel-1.5.0-svn/log.valgrind
> ==00:00:05:18.814 14193==    <inherited from parent>
> ==00:00:05:18.814 14193==
> ==00:00:05:18.814 14193== Open file descriptor 2: /dev/null
> ==00:00:05:18.814 14193==    <inherited from parent>
> ==00:00:05:18.814 14193==
> ==00:00:05:18.814 14193== Open file descriptor 1: /dev/null
> ==00:00:05:18.814 14193==    <inherited from parent>
> ==00:00:05:18.814 14193==
> ==00:00:05:18.814 14193== Open file descriptor 0: /dev/null
> ==00:00:05:18.814 14193==    <inherited from parent>
> ==00:00:05:18.814 14193==
> ==00:00:05:18.814 14193==
> ==00:00:05:18.814 14193== ERROR SUMMARY: 0 errors from 0 contexts
> (suppressed: 8 from 1)
> ==00:00:05:18.814 14193== malloc/free: in use at exit: 1,840 bytes in 
> 27 blocks.
> ==00:00:05:18.814 14193== malloc/free: 2,525,985 allocs, 2,525,958 
> frees,
> 325,327,112 bytes allocated.
> ==00:00:05:18.814 14193== For counts of detected errors, rerun with: 
> -v
> ==00:00:05:18.814 14193== searching for pointers to 27 not-freed blocks.
> ==00:00:05:18.832 14193== checked 1,748,080 bytes.
> ==00:00:05:18.832 14193==
> ==00:00:05:18.832 14193== LEAK SUMMARY:
> ==00:00:05:18.832 14193==    definitely lost: 0 bytes in 0 blocks.
> ==00:00:05:18.832 14193==      possibly lost: 0 bytes in 0 blocks.
> ==00:00:05:18.832 14193==    still reachable: 0 bytes in 0 blocks.
> ==00:00:05:18.832 14193==         suppressed: 1,840 bytes in 27 blocks.
>
> anyone being able to reproduce the leak? Please report.
>
> Stipe
>
> --
> -------------------------------------------------------------------
> K?lner Landstrasse 419
> 40589 D?sseldorf, NRW, Germany
>
> tolj.org system architecture      Kannel Software Foundation (KSF)
> http://www.tolj.org/              http://www.kannel.org/
>
> mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
> -------------------------------------------------------------------
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.kannel.org/pipermail/devel/attachments/20140607/bbc2b334/attachm
ent-0001.html>




Reply via email to