gala crashed with SIGSEGV in meta_workspace_index()

[zpzgone]

Gala crashes on opening autocomplete window in JetBrains IDEs (PhpStorm, RubyMine, etc)

ProblemType: Crash
DistroRelease: elementary OS 0.2
Package: gala 0.1-0~r264+pkg15~precise1 [origin: LP-PPA-elementary-os-daily]
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
Uname: Linux 3.2.0-32-generic-pae i686
ApportVersion: 2.0.1-0ubuntu15+elementary3~precise1
Architecture: i386
CrashCounter: 1
CrashDB: gala
Date: Tue Nov 27 16:39:49 2012
ExecutablePath: /usr/bin/gala
InstallationMedia: elementary OS 0.2 "Luna" - Beta 1 i386 (20121114)
MarkForUpload: True
ProcCmdline: gala
SegvAnalysis:
 Segfault happened at: 0xb77729c7 <meta_workspace_index+23>: mov 0xc(%eax),%eax
 PC (0xb77729c7) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gala
StacktraceTop:
 meta_workspace_index () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 meta_window_foreach_ancestor () from /usr/lib/libmutter.so.0
 meta_window_change_workspace () from /usr/lib/libmutter.so.0
Title: gala crashed with SIGSEGV in meta_workspace_index()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[RabbitBot (rabbitbot-a)]

StacktraceTop:
 meta_workspace_index () from /tmp/tmplZbDDI/usr/lib/libmutter.so.0
 ?? () from /tmp/tmplZbDDI/usr/lib/libmutter.so.0
 ?? () from /tmp/tmplZbDDI/usr/lib/libmutter.so.0
 meta_window_foreach_ancestor () from /tmp/tmplZbDDI/usr/lib/libmutter.so.0
 meta_window_change_workspace () from /tmp/tmplZbDDI/usr/lib/libmutter.so.0

[Sergey "Shnatsel" Davidoff (shnatsel)]

Screencast of the issue is available at https://bugs.launchpad.net/gala/+bug/1082878/comments/3

[Sergey "Shnatsel" Davidoff (shnatsel)]

Another screencast and some debuggin info is available in bug 1078126

[Sergey "Shnatsel" Davidoff (shnatsel)]

Elevating importance and targeting to beta2 because a duplicate bug has such status.

[Tom Beckmann (tombeckmann)]

From reading the backtraces I thought it may be related to the minimize animation (which was applied on any window type up to now), although I could be wrong as the animation name is nowhere directly given in the trace and the line numbers apparently changed since it was generated.
So maybe, just maybe, it could work now, as we no longer animate non-normal window minimizing.

[Sergey "Shnatsel" Davidoff (shnatsel)]

Marking incomplete until somebody reproduces witha version later than... which one, exactly?