On Tue, May 22, 2012 at 08:07:38AM +0200, Raphael Manfredi wrote: > Despite the known latent memory bugs, I have decided to code-freeze the > current git "devel" branch and make it a candidate release. > > There are two main memory bugs that I know of: a huge memory leak (only > witnessed by one person, systematicallu) and a random malloc() freelist > corruption that happens from time to time.
I hope I'm not suggesting something you already know but have you given Valgrind a go? I tend to track their SVN but they have just released a new version in the last few months. Aside from the default memcheck tool there are also massif (heap profiling) and sgcheck (stack and array overrun) worth running. > Please make sure to grab the latest "devel" branch and test it thoroughly > if you can recompile your gtk-gnutella. I'm planning to release at the > beginning of June, in roughly two weeks. Changes to "devel" will now be > limited to bug fixes, no new features. > > Thanks for your support during this testing phase, especially on 64-bit > platforms and on Windows, which I don't easily have access to. Will do... -- Alex, homepage: http://www.bennee.com/~alex/ All the world's a stage and most of us are desperately unrehearsed. -- Sean O'Casey
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ gtk-gnutella-devel mailing list gtk-gnutella-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
