gnome-tweak-tool crashed with SIGSEGV in gdk_x11_window_get_xid()

[Wise Melon]

I went into gnome-tweak-tool, disabled all my extensions which were enabled, and then did 'ALT + F2' in order to run 'r' to restart gnome-shell. Almost immediately after the restart, gnome-tweak-tool suddenly quit.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: gnome-tweak-tool 3.18.0-1~wily1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Feb 3 16:33:50 2016
ExecutablePath: /usr/bin/gnome-tweak-tool
InstallationDate: Installed on 2015-12-10 (55 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-tweak-tool
SegvAnalysis:
 Segfault happened at: 0x7ff30c5533a2: cmp %rdi,0xe8(%rdi)
 PC (0x7ff30c5533a2) ok
 source "%rdi" ok
 destination "0xe8(%rdi)" (0x000000e8) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-tweak-tool
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gdk_x11_window_get_xid () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-xim.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-tweak-tool crashed with SIGSEGV in gdk_x11_window_get_xid()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm 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 #1510305, 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.