https://sourceforge.net/p/tinythread/bugs/2011-06-20T20:54:50ZRecent changes to bugs2011-06-20T20:54:50Z2011-06-20T20:54:50Zabihttps://sourceforge.net/u/abhirana/https://sourceforge.net9f161d954fa142c502dcc8c43847d586013611ab

<div class="markdown_content"><p>Hi</p> <p>first of all, thanks for the excellent code, I been using it for quite sometime and it has proved to be quite robust on all platforms i tested out with !</p> <p>the reason i am writing this bug report is because i think there is a small leak happening on the lines of <a href="http://tread.wordpress.com/2007/02/26/valgrind-and-pthread_create-memory-leak/" rel="nofollow">http://tread.wordpress.com/2007/02/26/valgrind-and-pthread_create-memory-leak/</a> . Though i might be totally wrong and not using the library in the correct manner.</p> <p>i use the tinythread++ with matlab's c interface and what was happening is after sometime the virtual memory usage got out of hand and the program crashed (what the program did was in a loop start-&gt;spawn number of threads-&gt;stop). after running valgrind, checking via pmap and writing a test case it seems that the something with pthreads was being left on the stack and that caused lots of page faults and thus an increase in virtual memory.</p> <p>i guess it has something to do with pthread_exit(NULL) not being in the callee function perhaps?</p> <p>attached file compiled as g++ mex_example.cpp tinythread/tinythread.cpp -lpthread<br /> valgrind check done as valgrind -v --error-limit=no --tool=memcheck --track-origins=yes --leak-check=full --show-reachable=yes --num-callers=50 ./a.out</p> <p>tinythread++ version in matlab after running it for 100 iteration causes a virtual memory size of 77G whereas pthread version doesot leak any memory. BTW same with the c version, if you put a getchar at the end it seems to still increase memory using even when delete is used..</p> <p>thanks again.</p></div>