WebKitWebProcess crashed with SIGSEGV in WTFCrash()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| webkit2gtk (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
apport just popped up a message that a problem was detected, however my browser is still running fine, and all my tabs show their contents, I do see the crashed in dmesg though:
[Fri Mar 9 23:08:25 2018] WebKitWebProces
[Fri Mar 9 23:11:51 2018] WebKitWebProces
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: libwebkit2gtk-
ProcVersionSign
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 9 23:08:26 2018
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-12-02 (97 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/zsh
SegvAnalysis:
Segfault happened at: 0x7f3de963b29c <WTFCrash+28>: movl $0x0,(%rax)
PC (0x7f3de963b29c) 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 () at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: WebKitWebProcess crashed with SIGSEGV in WTFCrash()
UpgradeStatus: Upgraded to bionic on 2018-02-24 (13 days ago)
UserGroups: adm cdrom dialout dip libvirt lp lpadmin plugdev sambashare sudo
| Török Edwin (edwintorok) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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.