Comment 2 for bug 694528

Hello Paul
Yes, I can reporduce it.
I've found that ffmpeg is running at 100% of cpu, when shell crash, and winff don't crash, go on in his work.
The messages in the shell terminal:
Avviso del window manager: Log level 16: STACK_OP_ADD: window 0x1200012 already in stack
Avviso del window manager: Log level 16: STACK_OP_ADD: window 0x1200012 already in stack
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x1200008 non valido per 0x1200133 (Indice AVI).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x1200008 non valido per 0x1200544 (Correzione).
Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400075 (WinFF)
Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avviso del window manager: Log level 16: invalid unclassed pointer in cast to `GObject'
Avviso del window manager: Log level 8: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
Shell killed with signal 11
njin@Lucid:~/gnome-shell/source/gnome-shell/src$ Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x1200008 non valido per 0x1200544 (Correzione). [Advice of window manager:Specified a WM_TRANSIENT_FOR window 0x1200008 not valid for 0x1200544 (Correction)].
When possible i will try on another machine to see if reproduceable there too.
Thanks
Fabio