gnome-shell crashed with SIGSEGV in meta_monitor_config_update_current()

[Nazar Mokrynskyi]

I have TV Seiki SE39UY04 with 4k resolution.
For games I want to change it to 1080p, but got this crash instead (half of times, half just remains with 4k resolution).

As TV is connected to laptop with 1080p display (which is usually turned off), I found one workaround:
1) enable laptop display
2) change TV resolution to 1080p (sometimes crashes at this place, once per each 5 successful)
3) disable laptop display

Really annoying bug.

This time it crashed ad step 2 Two times.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.12.1-0ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging]
Uname: Linux 3.15.0-rc5-haswell x86_64
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu May 15 06:11:48 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2012-04-27 (747 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7fbd9a8cf7d3 <meta_monitor_config_update_current+195>: movss 0x10(%rcx),%xmm0
 PC (0x7fbd9a8cf7d3) ok
 source "0x10(%rcx)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_monitor_config_update_current () from /usr/lib/libmutter.so.0
 ?? () from /usr/lib/libmutter.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in meta_monitor_config_update_current()
UpgradeStatus: Upgraded to trusty on 2013-05-12 (367 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

[Ubuntu GNOME (ug-bot)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1254560, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Nazar Mokrynskyi (nazar-pc)]

It is not duplicate bug because there was some problems with previous and it was declined.