On Wed, Nov 03, 2004 at 09:32:15AM +0100, Roberto A. Foglietta wrote:
Roberto A. Foglietta wrote:
Hi,
I didn't find memory leak bug but I have to say this: waiting html page load complete doesn't help.
I have done a patch which after first load doesn't show images BUT I lost it because I didn't care it... But when I saw my logs I see that patch fixed memory leak. Even if memory leak has nothing to do with images because trivial pages has no images. Probably 4kb is a structure not data.
Thinking memory leak is generated by losing a structure instead data could explain why has fixed size (4kb for each reload) and probably why it happen only during a reload. In reload some data is cached but structures a created and destroyed... probably not all of them.
Unfortunately it's time I have to find another browser to use it in my project. Sorry.
Suggest:
Yes, I haven't used it in a long time. Good to remember. After upgrading to valgrind-2.2.0, and testing, it detected two minor leaks in Dillo (fixed now in CVS), but these were not the cause for the "reload" leak. After that, I got no more leak errors detected inside Dillo (while testing a trivial page with 12 reloads) with: valgrind --tool=addrcheck --leak-check=yes ./dillo /tmp Interesting to note is this one in GTK+: ==9413== ==9413== ==9413== 2816 bytes in 36 blocks are definitely lost in loss record 47 of 54 ==9413== at 0x34148F1D: calloc (in /usr/lib/valgrind/vgpreload_addrcheck.so) ==9413== by 0x34343F2A: g_malloc0 (in /usr/lib/libglib-1.2.so.0.0.10) ==9413== by 0x342C12AA: gtk_type_new (in /usr/lib/libgtk-1.2.so.0.9.1) ==9413== by 0x34284C27: gtk_pixmap_new (in /usr/lib/libgtk-1.2.so.0.9.1) ==9413== -- Cheers Jorge.-