Bug 662071-[Win32]-Don't init the Big Clutter Lock
authorChun-wei Fan <fanchunwei@src.gnome.org>
Mon, 24 Oct 2011 16:13:53 +0000 (00:13 +0800)
committerChun-wei Fan <fanchunwei@src.gnome.org>
Mon, 24 Oct 2011 16:13:53 +0000 (00:13 +0800)
commit7c6038d77b0d0b3323867f8a881d72ca37bb8b7c
tree5756e39b8905471a524818ab38c1f05c2dad852d
parent0f9eded1c33c5c41157989f092bb6a47b535ea97
Bug 662071-[Win32]-Don't init the Big Clutter Lock

Since the Windows GUI system is assuming multithreadedness, initializing
locks after entering the GUI portion on Windows is likely to cause
problems[1][2], which results many Clutter programs to crash due to
releasing resources that they did not own.

[1]: Multi-threaded use of GTK+ on Win32 in README.win32 of GTK+
     source package
[2]: Explanation of Windows GUI system regarding its multithreadness
     assumptions-
     http://mail.gnome.org/archives/gtk-list/2011-June/msg00005.html
clutter/clutter-main.c