Good lord, I think I've finally tracked this down. Turns out it's not a PyGTK issue after all, but a zlib one. Some of the data that my application is loading is zlib-compressed, and I've been using zlib.decompress() to load it in. It turns out that for larger files, if I don't specify "bufsize," the malloc()s that it's doing behind-the-scenes are clobbering memory, which was leading to all the real bizarre behavior I was seeing before.
Once I've got my wits about me, tomorrow, I'll put together a little testcase and submit the bug to Python's tracker. Thanks for the responses, etc! Sorry to bug everyone with something that turned out to be not a PyGTK issue after all... -CJ -- WOW: Flemmy | "Happiness isn't good enough for me! I [email protected] | demand euphoria!" 24.24.2.3171 | - Calvin _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
