WebKitWebProcess crashed with SIGSEGV in WTFCrash()

[craig leibbrand]

I don't know where the error occurred. I was working in Chrome beta browser, accessing google drive, microsoft onedrive, yahoo, outlook. Mozilla firefox was open, javascript off, looking at startribune.com

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: libwebkit2gtk-4.0-37 2.20.0-1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Mar 13 12:09:13 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
InstallationDate: Installed on 2018-03-10 (3 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 1 17
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f7ab7a8b28c <WTFCrash+28>: movl $0x0,(%rax)
 PC (0x7f7ab7a8b28c) ok
 source "$0x0" ok
 destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: webkit2gtk
StacktraceTop:
 WTFCrash () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
Title: WebKitWebProcess crashed with SIGSEGV in WTFCrash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare 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 #1752108, 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.