CJ Kucera wrote: > David Ripton wrote: > > Utterly terrifying that something as fundamental as zlib would be broken > > on a platform as common as Windows.
One final update on this... Since I've impugned on zlib's otherwise sparkling reputation, I feel that I should mention that it turns out that it *was* PyCairo which was clobbering memory, and not zlib. The changes that I had made in how zlib was called was merely changing the memory allocation scheme sufficiently that PyCairo's leakage was no longer apparent. Anyway, there's a fix in PyCairo's CVS now, so all should be well once the next version gets released. -CJ -- WOW: Flemmy | "The ships hung in the sky in much the same [email protected] | way that bricks don't." - Douglas Adams, 24.24.2.3171 | _The Hitchhiker's Guide To The Galaxy_ _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
