I have no idea. I posted a forum post with Chromer, stepped away from the computer, came back to this error message.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: libwebkit2gtk-4.0-37 2.14.0-1
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Oct 9 13:09:21 2016
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
InstallationDate: Installed on 2016-08-26 (43 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160824.1)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 51
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f89739fb009: jmpq *0x1570(%rax)
PC (0x7f89739fb009) ok
source "*0x1570(%rax)" ok
SP (0x7ffdf77d5228) ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: webkit2gtk
StacktraceTop:
?? () from /usr/lib/nvidia-367/libGLdispatch.so.0
?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
__run_exit_handlers (status=0, listp=0x7f898281e5d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83
__GI_exit (status=<optimised out>) at exit.c:105
Title: WebKitWebProcess crashed with SIGSEGV in __run_exit_handlers()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape video
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 #1630437, 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.