On Mon, Jan 26, 2009 at 11:03:20PM +0100, Hofmann Johannes wrote:
On Mon, Jan 26, 2009 at 09:22:03PM +0000, Jeremy Henty wrote:
Valgrind reports that <ol>s leak the labels of their items: each of the first 9 <li>s leaks 3 bytes, then they leak 4 bytes per <li> etc. The leaked memory is created by the line
list_item->initWithText (dStrdup(buf), wordStyle);
Ah right. The strdup() can just be dropped. Allocation and deallocation of text is done in Textblock itself for quite some time now. Please check current tip.
It's fixed! (/me deletes valgrind suppression file) But..., valgrind still reports some "indirectly lost" blocks despite reporting no "definitely lost" or "possibly lost" blocks. How is that possible? I am suppressing some leaks that come from the depths of X windows and other libraries, could that be the reason? (Of course this may have nothing to do with Dillo.) Regards, Jeremy Henty