From my experience, when you get crashes sometimes when running a gui, like Wx, it usually comes down to a timing problem in the eventloop compounded by differing system loads. What I mean is if your code is improperly finishing, by destroying a widget at the wrong time, or whatever, it sometimes will run ok if the gui program has full cpu access, but another time, when the system load is high, the gui's event-loop may get delayed in performing, and an odd crash may occur. It has got to be something in your code, please show it. If it comes when you destroy a frame, it may be possible that a child of that frame isn't destroying itself first, or some other esoteric timing error.