Comment 84 for bug 226470
Revision history for this message
|
|
#84 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
David, understood.
If indeed all Gtk/glib requests are being submitted through the main thread, there should *still* be a constraint that they should *NOT* be submitted while a window deletion is in progress. Indeed, all frames, windows, etc. should have a flag indicating that "modifications to this window/frame will be bounced" and such a flag should be set once a window destruction (or redraw) process is invoked.
The form of the error, i.e. "Window unexpectedly destroyed" followed by several window data structure consistency checks reeks of the fact that one is adding things to do to windows that are in the middle of the downwards spiral for destruction. That is a really bad idea. One should not be attempting to schedule activities for windows which are effectively dead!
Robert