Bug 672600 – Mutter 3.3.92 crashes when windows were minimized.

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 672600 - Mutter 3.3.92 crashes when windows were minimized.


Summary:	Mutter 3.3.92 crashes when windows were minimized.


Status:	RESOLVED DUPLICATE of bug 673809

Product:	mutter
Classification:	Core
Component:	general
Version:	3.3.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	mutter-maint
QA Contact:	mutter-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-03-22 02:02 UTC by Hirotaka Maruyama
Modified:	2012-04-17 17:36 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
proposed patch (1.28 KB, patch) 2012-03-30 17:13 UTC, Pavel Vasin	none	Details \| Review

Description Hirotaka Maruyama 2012-03-22 02:02:04 UTC

Recently I've experienced that on "stand-alone" mutter session in Ubuntu 12.04 Beta...

Mutter seems to crash on Whenever I clicked minimize button on window title, and keyboard shortcut were pressed as well.

So gdb says:

----------------------------------------------------------------------------------------------
GNU gdb (Ubuntu/Linaro 7.4-2012.02-0ubuntu2) 7.4-2012.02
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/mutter...Reading symbols from /usr/lib/debug/usr/bin/mutter...done.
done.
(gdb) r
Starting program: /usr/bin/mutter 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea8f4700 (LWP 2241)]
[New Thread 0x7fffea0f3700 (LWP 2242)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff73af561 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
-------------------------------------------------------------------------------------------------

You could see "segfault" in that last part of log.
As far as I know why it happened, but remembered well, 3.3.90 didn't do that.
Anyway, The mystery is that gnome-shell 3.3.92 session works pretty good, Only I encountered it on mutter session something like gnome-fallback session.

Anyone could confirm it? :)

Comment 1 André Klapper 2012-03-22 09:46:33 UTC

"thread apply all bt" will print a stacktrace. Please paste it here, and make sure that you have debug symbols installed.

Comment 2 Hirotaka Maruyama 2012-03-22 11:33:04 UTC

(In reply to comment #1)
> "thread apply all bt" will print a stacktrace. Please paste it here, and make
> sure that you have debug symbols installed.

Hi André.

Unfortunately I could not...
Because this time mutter completely crashed so I could not click any windows, not inputting any chars on terminal and so... :(

Only what I could do is press Ctrl+Alt+BS to kill Xorg...

Or is there any way to continue to backtracing via other VT?

Best Regards.

Comment 3 Pavel Vasin 2012-03-30 17:11:24 UTC

backtrace:

+ Trace 229982

#0 __strlen_sse2_bsf
from /lib/libc.so.6
#1 g_str_has_prefix
from /usr/lib/libglib-2.0.so.0
#2 ??
from /usr/lib/libclutter-1.0.so.0
#3 clutter_actor_animate
from /usr/lib/libclutter-1.0.so.0
#4 minimize
at default.c line 477
#5 meta_plugin_manager_event_simple
at compositor/meta-plugin-manager.c line 276
#6 start_simple_effect
at compositor/meta-window-actor.c line 1080
#7 meta_window_actor_hide
at compositor/meta-window-actor.c line 1438
#8 meta_compositor_hide_window
at compositor/compositor.c line 843
#9 meta_window_hide
at core/window.c line 3247
#10 implement_showing
at core/window.c line 2231
#11 idle_calc_showing
at core/window.c line 2358
#12 run_repaint_laters
at core/util.c line 794
#13 ??
from /usr/lib/libclutter-1.0.so.0
#14 ??
from /usr/lib/libclutter-1.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 meta_run
at core/main.c line 555
#19 main
at core/mutter.c line 96

Comment 4 Pavel Vasin 2012-03-30 17:13:18 UTC

Created attachment 210986 [details] [review]
proposed patch

Comment 5 Owen Taylor 2012-04-17 17:36:25 UTC

Thanks for this fix. It looks like Giovanni later duplicated the effort - we have committed:

$ git show 3aad30143c0abdf24bfbaa12454cfeba6b8047ab
commit 3aad30143c0abdf24bfbaa12454cfeba6b8047ab
Author: Giovanni Campagna <gcampagna@src.gnome.org>
Date:   Tue Apr 10 03:43:09 2012 +0200

    default plugin: use the right type for varargs
    
    Coordinates in Clutter are double, so twice the size of an int, and
    if not correctly casted memory corruption occurs.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=673809

Sorry we missed this.

*** This bug has been marked as a duplicate of bug 673809 ***