I REALLY understand chasing the leaks and then finding something like this stings ... / regars, Lars Segerlund. On Thu, 25 Nov 2004 12:23:22 -0300 Jorge Arellano Cid <jcid@dillo.org> wrote:
Hi,
Well, I searched for where to report bugs in pthreads and the process is tedious to say the least.
They want the submitter to test against CVS glibc which is a thing I don't have the time, nor the machine to do.
FWIW, a near target is at least the test program on the latest glibc (glibc-2.3.3 at this time), but I have 2.3.2. Can someone please test it with glibc-2.3.3?
If the Solaris test shows no leaks, then that's strong evidence of a _serious_ problem within glibc's pthreads and the bug report will most probably be welcomed.
After I have the results from glibc-2.3.3 and Solaris, I'll send the report. In the meanwhile I've been playing some workarounds for Dillo and the results is an impressive memory usage reduction so far (BTW, the reload memory leak also had its roots in pthreads leaking memory).
What an irony: after years of chasing the most minor memory leaks (up to a few bytes), it ends up being that we've leaked a lot, by Megabyte units, because of an external library.
Notwithstanding there's still the possibility of me being wrong in the understanding of its API, this chance is growing thiner.
It could also be the kernel (or ps) not reporting correctly the VSZ and RSS. Who knows? At least the workarounds are improving a lot these stats in my tree.
-- Cheers Jorge.-
_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev