GNOME Bugzilla – Bug 353513
Crash when dragging newly opened window with meta-drag
Last modified: 2009-12-04 04:58:37 UTC
I've been seeing a fairly frequent (although not trivially reproducible) SIGABRT crash in metacity 2.14.5 (Debian unstable) when doing a meta-click-drag on a freshly appeared window. So far I've yet to see it with a regular titlebar drag, or with a window that's been visible for more than half a second or so. The former might be caused by the extra time necessary to aim at and hit the titlebar, though. I also haven't seen it except with gnome-terminal windows, but since I open lots more of those than anything else that could simply be the odds. Here's a stack trace, though not a very good one. Program received signal SIGABRT, Aborted. [Switching to Thread 47532730492480 (LWP 23990)] 0x00002b3b123ee07b in raise () from /lib/libc.so.6 (gdb) thread apply all bt
+ Trace 71240
Thread 1 (Thread 47532730492480 (LWP 23990))
meta_rectangle_edge_aligns() has a short switch statement followed by a g_assert_not_reached(). From the stack trace, it appears you hit the assertion, meaning that the edge passed in was uninitialized somehow. Since this is a meta-click-drag instead of meta-shift-click-drag, the call had to originate from edge-resistance.c:apply_edge_resistance(). I'm not sure what'd cause that though...
Similar Ubuntu bug: https://launchpad.net/products/metacity/+bug/64009 "Metacity crashed for me while draging a window around (pressing the ALT key and moving the mouse). ... Attached is the apport backtrace.These lines are the last messages from .xsession-errors: ... Window manager warning: Log level 6: file bo xes.c: line 1078 (meta_rectangle_edge_aligns): should not be reached ... http://librarian.launchpad.net/4661665/_usr_bin_metacity.1000.crash ... Package: metacity 1:2.16.3-0ubuntu1 ..."
Does this crash happen when the window being moved is part way off the screen? Does the patch I'm about to attach solve the problem?
Created attachment 74027 [details] [review] Possible fix
the submitter said that a part was under the panel and a part might have been off-screen, he's not sure about it I've uploaded a package to edgy with the patch, the crash doesn't happen that often to him (like once a week), it might take some time to have an idea if that fixes the issue
Although I can't pinpoint the /exact/ time of the crash, I can reproduce this crash /somewhat/ consistently. My setup: - Dual head. I am using nvidia drivers (Option "TwinViewOrientation" "RightOf"), this is a laptop and an external monitor. With both displays, an effective desktop size of 2720 x 1024 - ONLY happens when in twinview and external monitor - Unbuntu Edgy 6.10 [metacity 1:2.16.3-0ubuntu2] (which includes patch 74027) - Had same issues with older version of Ubuntu Dapper 6.06/nvidia twinview (didnt file bug then as was hoping it was a transient bug) - all window movements are done via a "regular titlebar drag" Extreme inconsistency in reproducing the crash, but I have always been able to cause a crash eventually (in under 60 seconds) Sometimes it wont crash with the first selected window and must drag a different window and start moving that one around. It appears that it only happens when dragging a window from one screen to the other, or if part of the window crosses over to the other screen as if i create a small window and make sure it remains on one screen it seems to be stable. What I have done as a /workaround/ is to never make large drag movements, especially when moving from one screen to the next. I drag the window only short distances and then drop and pickup. When run from console window, here is the error: Window manager warning: Log level 6: file boxes.c: line 1078 (meta_rectangle_edge_aligns): should not be reached Aborted (core dumped) If there is something I can do to produce better debug info, please let me know what to do.
*** Bug 385923 has been marked as a duplicate of this bug. ***
I've got three monitors (two on an nVidia card, and one on a matrox), and I get the exact same error as Flavio daCosta. From testing for about one minute, I got metacity to crash about three times, each time being while a window was dragged from one screen to another. The crash occurs whether it's a normal title bar drag or an alt+click drag.
I committed the patch, since it can't hurt and at least will help. It'd be really nice if someone who can reproduce could install debugging symbols and get a full stack trace.
*** Bug 434392 has been marked as a duplicate of this bug. ***
Now that the patch has been in for a while, is anyone still experiencing this?
I am no longer able to reproduce this crash. - Same physical setup as above. - metacity 2.22.0 (Ubuntu hardy 8.04.1 metacity pkg 1:2.22.0-0ubuntu4)
The bug is reproducible on my laptop, mostly if i move a window between monitors. Metacity error: metacity: ERROR:(core/boxes.c:11128):meta_rectangle_edge_aligns: code should not be reached My setup is: Metacity version: 2.22.0 System: Gentoo Two monitors with radeon driver: $ xrandr Screen 0: minimum 320 x 200, current 3000 x 1200, maximum 3008 x 1200 VGA-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm 1600x1200 60.0*+ 59.9 1280x1024 75.0 59.9 1152x864 74.8 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 LVDS connected 1400x1050+1600+0 (normal left inverted right x axis y axis) 0mm x 0mm 1400x1050 60.0*+ 1024x768 60.0 800x600 60.3 640x480 59.9 S-video disconnected (normal left inverted right x axis y axis)
Created attachment 122491 [details] metacity strace There is a strace of the bug reproduced by moving an vmware-player window.
Hey Andreas, thanks for your comment. The thing you've attached is an strace log, not a stacktrace :( Can you still reproduce this issue? If so, please see http://live.gnome.org/GettingTraces and get us a stacktrace with debug symbols :)
Closing this bug report as no further information has been provided. Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 2.28.0 or later, thanks.