Just to tell you, version 2.2.0 is also available online...<br><br>Steven, I also noticed this one time leak, is there a way to get rid of them?<br><br><br>Thx<br><div class="gmail_quote">2009/8/15 moises acuna <span dir="ltr"><<a href="mailto:moises.acuna@gmail.com">moises.acuna@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Steven and Steven,<br>Thankfully the bug was simpler than I was expecting, it was an issue with the version 2.0.2, i upgrated to v 2.1.1rc10 and the wrong behauviour stopped. Just for documentation: was this any known issue ? <br>
Thank you very much for your help. <br><br><div class="gmail_quote">2009/8/14 Steven Dorigotti <span dir="ltr"><<a href="mailto:dorigotti@koanlogic.com" target="_blank">dorigotti@koanlogic.com</a>></span><div><div>
</div><div class="h5"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div>Hello Moises,</div><div><br></div><div> what you are seeing is a one-time leak upon initialisation of the embedded file system.</div><div><br></div><div> So it is not connected to the problems you are having upon refresh. Either: </div>
<div><br></div><div>- some info is missing (did you run your full previous test case, with refreshes, under valgrind?);</div><div>- or the problems you are having might be caused by something external (e.g. uclibc problem which causes kloned process to grow). </div>
<div><br></div><div> Do you have a reference linux distribution with that version of uclinux, so we can find an iso (or is it custom)? Any other info?</div><div><br></div><div>cheers,</div>sd<div><div></div><div>
<div><br></div><div><br><div><div>On 12/ago/09, at 19:54, moises acuna wrote:</div><br><blockquote type="cite">Hi Steven,<br>thanks for the response. <br>first i tried with a reduced version of the project, but it's still growing with every refresh. So i tried it with Valgrind and it seems that the leak is in some KLone files. <br>
this is the report:<br><br>--3673-- supp: 21 dl-hack3-1<br>==3673== malloc/free: in use at exit: 1,996 bytes in 99 blocks.<br>==3673== malloc/free: 8,305 allocs, 8,206 frees, 5,136,560 bytes allocated.<br>==3673== <br>
==3673== searching for pointers to 99 not-freed blocks.<br>==3673== checked 331,292 bytes.<br>==3673== <br>==3673== 1,988 (1,808 direct, 180 indirect) bytes in 89 blocks are definitely lost in loss record 3 of 3<br>==3673== at 0x4021BDE: calloc (vg_replace_malloc.c:397)<br>
==3673== by 0x80953D9: u_zalloc (memory.c:63)<br>==3673== by 0x80910CC: u_hmap_o_new (hmap.c:1072)<br>==3673== by 0x8075D9E: emb_register (emb.c:69)<br>==3673== by 0x807F926: module_init_2c8d30e5acaba22237ea983216ef3130 (pg_2c8d30e5acaba22237ea983216ef3130.c:50)<br>
==3673== by 0x807AA41: do_register (register.c:22)<br>==3673== by 0x807AA29: register_pages (register.c:9)<br>==3673== by 0x8075BA1: emb_init (emb.c:32)<br>==3673== by 0x8050C3D: app_init (main.c:96)<br>==3673== by 0x805130C: main (entry.c:397)<br>
==3673== <br>==3673== LEAK SUMMARY:<br>==3673== definitely lost: 1,808 bytes in 89 blocks.<br>==3673== indirectly lost: 180 bytes in 9 blocks.<br>==3673== possibly lost: 0 bytes in 0 blocks.<br>==3673== still reachable: 8 bytes in 1 blocks.<br>
==3673== suppressed: 0 bytes in 0 blocks.<br><br><br><br><br>by 0x807F926: module_init_2c8d30e5acaba22237ea983216ef3130 (pg_2c8d30e5acaba22237ea983216ef3130.c:50)<br><br>this one is generated in the site. It says that the leak is in this function:<br>
<br>void module_init_2c8d30e5acaba22237ea983216ef3130(void) <br>{ <br> res_ctor(); <br> emb_register((embres_t*)&e); <br>} <br><br>i don't know if this is some kind of a bug or something. <br>
<br>The problem here is that the kloned process in the uCLinux is growin and growing with every refresh and after 3 days running the server will have an stack overflow or something. This doesn't happen in Ubuntu. <br>
<br>Thanks for any help with this. <br><br><br><br><div class="gmail_quote">2009/8/11 Steven Van Ingelgem <span dir="ltr"><<a href="mailto:steven@vaningelgem.be" target="_blank">steven@vaningelgem.be</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> You can try running it through valgrind:<br><br>valgrind -v --leak-check=full ./kloned<br>
<br>
<br>After you have done running the pages, you can see if it is truly a leak or not.<br><br><br>--<br>Steven<br><a href="http://www.salvania.be" target="_blank">www.salvania.be</a><br> <br><div class="gmail_quote">2009/8/12 moises acuna <span dir="ltr"><<a href="mailto:moises.acuna@gmail.com" target="_blank">moises.acuna@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div><div></div><div> Hello everyone,<br>i'm having trouble with the Klone server over uClinux. The kloned process memory allocation is getting bigger and bigger every refresh of a page (i have an option in a page to turn on or off an every-5-seconds-autorefresh), but this happens only in uClinux , with Linux( Ubuntu 8.04) this doesn't happens. The process stays stable there. I've been trying to manage the memory for arrays and everything the best way possible and not leaving any pointer hanging. Have you ever had a problem like this. Am I missing something. Thanks for any help. <br>
<br>pd. the uclinux version is v3.2.0.ANI0803 <br><font color="#888888"><br><br clear="all"><br>-- <br>Moisés AAC<br> </font><br></div></div>_______________________________________________<br> Klone-users mailing list<br>
<a href="mailto:Klone-users@koanlogic.com" target="_blank">Klone-users@koanlogic.com</a><br> <a href="http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users" target="_blank">http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users</a><br>
<br></blockquote></div><br> <br>_______________________________________________<br> Klone-users mailing list<br> <a href="mailto:Klone-users@koanlogic.com" target="_blank">Klone-users@koanlogic.com</a><br> <a href="http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users" target="_blank">http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Moisés AAC<br> _______________________________________________<br>Klone-users mailing list<br><a href="mailto:Klone-users@koanlogic.com" target="_blank">Klone-users@koanlogic.com</a><br>
<a href="http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users" target="_blank">http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users</a><br></blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
Klone-users mailing list<br>
<a href="mailto:Klone-users@koanlogic.com" target="_blank">Klone-users@koanlogic.com</a><br>
<a href="http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users" target="_blank">http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users</a><br>
<br></blockquote></div></div></div><font color="#888888"><br><br clear="all"><br>-- <br>Moisés AAC<br>
</font><br>_______________________________________________<br>
Klone-users mailing list<br>
<a href="mailto:Klone-users@koanlogic.com">Klone-users@koanlogic.com</a><br>
<a href="http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users" target="_blank">http://koanlogic.com/cgi-bin/mailman/listinfo/klone-users</a><br>
<br></blockquote></div><br>