Hi Hanh,
Please you email us the file smsbox_memleakcheck_20140503.txt with your results from Valgrind, as it's no longer available on drop box. Thanks From: Alexander Malysh [mailto:[email protected]] On Behalf Of Alexander Malysh Sent: Friday, May 9, 2014 12:58 PM To: [email protected] Cc: Hanh Le Bich; [email protected]; Stipe Tolj; [email protected] Subject: Re: Does opensmppbox and smsbox have serious memory issues? Hi, unfortunately this file is not there anymore. Could you please new file please? Alex Am 07.05.2014 um 13:15 schrieb [email protected]: HI Hanh and Kannel developers, The memory leaks in the latest svn for smsbox, as mentioned in your post Date: Sat, 3 May 2014 10:06:54 +0700 and shown in <https://www.dropbox.com/s/yjrc6wmdm0rwonz/smsbox_memleakcheck_20140503.txt> https://www.dropbox.com/s/yjrc6wmdm0rwonz/smsbox_memleakcheck_20140503.txt are also contributing to the increase in the total memory leak. Each SMSs needs to also go through smsbox. There are memory leaks both smsbox and also in opensmppbox. Thanks for bringing this to the attention of the Kannel devel group and producing these Valgrinds. It's useful to see what happens to Kannel with a high throughput. This is currently not my area of expertise. We need the help of the top Kannel developers to fix this, so the latest svn will be free of memory leaks. You mention in the post on Sat, 3 May 2014 10:06:54 +0700: "Hello again, Here is valgrind report for the smsbox memory leaking. This is also the latest kannel revision 5089. For me, it still happen, i submit (broadcast) million SMS(s) per day within few hours at 1000 TPS of throughput. Thus each day, smsbox swallow ~ 400MB RAM and not release until server memory exhaust after few days. At this time, the box is auto restarted and i have my memory back, so on, again and again. I not sure, but in very low throughput system, i am not aware this issue. ==5730== LEAK SUMMARY: ==5730== definitely lost: 231,680 bytes in 14,480 blocks ==5730== indirectly lost: 144,790 bytes in 14,479 blocks ==5730== possibly lost: 0 bytes in 0 blocks ==5730== still reachable: 1,250 bytes in 40 blocks ==5730== suppressed: 0 bytes in 0 blocks ==5730== Reachable blocks (those to which a pointer was found) are not shown. ==5730== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==5730== ==5730== For counts of detected and suppressed errors, rerun with: -v ==5730== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 45 from 10)" rgds From: Hanh Le Bich [ <mailto:[email protected]> mailto:[email protected]] Sent: Wednesday, May 7, 2014 10:32 AM To: Rene Kluwen Cc: <mailto:[email protected]> [email protected]; <mailto:[email protected]> [email protected]; <mailto:[email protected]> [email protected] Subject: Re: Does opensmppbox and smsbox have serious memory issues? No Rene, i just monitor by some mem check tool. For example, htop tell me in the fist day, opensmppbox occupied 0.1% of RAM, the next 2 day is was 0.2%, and the 5th day, it is 0.3% now. Slowly increase. Regards, Hanh. On Wed, May 7, 2014 at 3:09 PM, Rene Kluwen < <mailto:[email protected]> [email protected]> wrote: Would you happen to have a valgrind output for this? == Rene From: Hanh Le Bich [mailto: <mailto:[email protected]> [email protected]] Sent: woensdag 7 mei 2014 9:20 To: <mailto:[email protected]> [email protected] Cc: Rene Kluwen; <mailto:[email protected]> [email protected]; <mailto:[email protected]> [email protected] Subject: Re: Does opensmppbox and smsbox have serious memory issues? Hello again, Hope you are doing great. After close monitoring opensmppbox after > 4 days continuous running, I just want to inform the mem leak still happen, the box is eating few tens (or nearly hundred) byte per day at throughput 100TPS (at max) and keep increasing. Regards, Hanh.
