GNOME Bugzilla – Bug 311819
Metacity crashes on certain windows
Last modified: 2005-07-29 08:00:12 UTC
Steps to reproduce: 1. Close all windows 2. Launch About GNOME 3. Witness metacity crash Stack trace:
+ Trace 62035
Other information: Attached is the output of metacity with METACITY_VERBOSE and METACITY_DEBUG set when this crash occurred.
Created attachment 49862 [details] Metacity debug output when crash occurs
According to simple-dup-finder this is a unique stack trace.
Created attachment 49874 [details] Another debug output I also see this crash when I open gaim Program received signal SIGSEGV, Segmentation fault.
+ Trace 62042
Thread NaN (LWP 17868)
Elijah, looks like this is from that recent patch.
Micahel's stack trace is different (though maybe just corrupted?), but yeah, Marcus' crash looks like it's clearly my fault. I think I know the problem, but I'll have to wait a few hours to take a closer look...
Created attachment 49891 [details] [review] Remove unsafe and overly-verbose debugging spew
So, um, I originally didn't mean to put that debugging information in avoid_being_obscured_as_second_modal_dialog() into the final patch. The if statement above was careful to order statements correctly to avoid a crash. The debugging stuff was just to help me verify everything was correct before submitting the patch. Apparently, when I was cleaning it all up to submit it, I for some reason decided to leave the debugging info there anyway but forgot to check that all the statements were valid... I don't think that debugging information is going to help much but it'd add lots of extra spew so let's just nuke it. Oh, and it's easier to reproduce than closing all windows--just enter show desktop mode first and then launch the dialog. Marcus, Michaël: could you verify that this fixes it for you? I'm pretty certain that this nails Marcus' bug, but Michaël's stack trace is busted--meta_window_place doesn't call meta_accel_label_set_accelerator which doesn't call meta_rectangle_intersect.
Of course, the patch solves the problem. Thanks.
*** Bug 311893 has been marked as a duplicate of this bug. ***
*** Bug 311707 has been marked as a duplicate of this bug. ***