dave wrote: > There's basically three ways we've been able to crash pygtk: > 1. TreeModels/TreeViews. These are touchy. Don't do things to them they > are not expecting or they die, and take Python.exe down too.
Hello, thanks for the response. It doesn't look like any of those really apply here... I do use a TreeView on my preferences screen, but removing it just makes the app crash on the first runthrough, isntead of waiting for the second. > 2. Dialog boxes (this is more of a freeze than a crash). We currently > wait a few seconds after displaying one to touch it, as they run their > own mainloop or something which tends to freeze up if you don't. I do have a couple of Dialog boxes in the app, though none are actually being used while I experience this issue (and as you mention, the problems you've seen isn't really a crash so much as a freeze, which isn't happening here). > 3. Psyco, the x86 optimizer. It works great, but randomly will crash > your application under load, which is non-optimal. And then, this one just doesn't apply to me. > Not sure if that helps! Certainly does - it's nice to see that someone else has at least seen that kind of crash before. I'm still incredibly mystified by it. I just don't see how adding a "pass" statement to a random function can mean the difference between a crash and a working app. Ditto for removing unused functions, etc... -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/
