> I'm building against GTK 2.10.4. It's pointless to report problems against such old versions. Even if there is a memory leak in GTK+ 2.10, nobody is going to fix it, and more importantly, nobody is going to release updated sources of it,when the current maintained version is 2.18. (Of course, you yourself, or your distro, or whoever, is free to continue to maintain the 2.10 branch in a separate "fork".) > Even with the suppressions, I'm getting lots of memory leaks reported. You should contemplate what you mean with "memory leak". If they are once-only allocations that appear to leak after the program has finished, they don't really matter, if you don't know whether they were leaked during the program execution or not. But do you see repeated leaks from the same location, with the number of repeats increasing the longer you let your code run, and the more "loops" you let its business logic go through? That then might be a true leak. --tml _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
