python3.6 crashed with SIGSEGV in WTFCrash()

[Brian Murray]

polychromatic-controller again

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: python3.6-minimal 3.6.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Tue Oct 17 09:37:56 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/python3.6
InstallationDate: Installed on 2013-01-16 (1735 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
ProcCmdline: polychromatic-controller
ProcEnviron:

Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f11144f5fcc <WTFCrash+28>: movl $0x0,(%rax)
 PC (0x7f11144f5fcc) ok
 source "$0x0" ok
 destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: python3.6
StacktraceTop:
 WTFCrash () at /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 webkit_web_view_run_javascript () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: python3.6 crashed with SIGSEGV in WTFCrash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo

[Apport retracing service (apport)]

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 #1712837, 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.