Hi there, Do you remember this 4KB memory leak mail-thread? On Thu, Oct 28, 2004 at 09:14:15AM +0200, Roberto A. Foglietta wrote:
robert w hall wrote:
Hmm - could this be distro/kernel dependent? Doing something similar (toggling reload when monitoring the dillo cvs page IIRC) and monitoring memory via top on a remote terminal shows No systematic effect - but this is playstation2-linux - an old 2.2.21 kernel on a redhat-like implementation for a mips.
In detail:- On first coming from the home page to the CVS changelog, top shows 9460k; this goes up to 9564 on first and stays there for subsequent presses of reload. Returning to Home then back to cvs recovers the 9460, 9564, 9564 sequence. Bob
It should be a glibc bug much more than kernel one, IMHO.
Sometimes (but very rarely) I supposed to have managed to fix it because I didn't see it anymore, but recompiling THE SAME code or simply restarting dillo I saw it again. Obviously I was reloading THE SAME trivial html page (html, head, body, 4 links in 4 rows, closing-end).
The pthreads bug was not deterministic, sometimes it got detached some others not, depending on the kernel scheduler and pthreads implementation.
I'm working on MDK 10.1 but I could test it on a slackware too. Or better I will test dillo running on A but compiled in B and all others combinations foreach A, B in {mdk,slack}.
At least after the pthread bug interim patch (CVS) it doesn't leak anymore in my system. And there's this gentle side effect of Dillo using less than 1/5 memory than before! -- Cheers Jorge.-