reopen 593356 found 593356 0.5.1-1 found 593356 0.5.3-1 found 593356 0.2.2-2 thanks
Hi, I think I found the real leak. It was obviously not found by valgrind before because the leaked resource was the internal thread memory. It's even worse, it was there almost from the beginning. Since the rest of my thread pool implementation was fine the problem has never been exposed unless the standby thread limit was hit which happened not that often. I still follow the mentioned plan, a small update of the Testing version with important patches will be available ASAP. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
