WebKitWebProcess crashed with SIGSEGV in WTFCrash()

Bug #1761966 reported by mikgr
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webkit2gtk (Ubuntu)
New
Undecided
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: libwebkit2gtk-4.0-37 2.20.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Apr 7 14:08:30 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
InstallationDate: Installed on 2018-03-23 (15 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180323)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 1 17
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb58ab732cc <WTFCrash+28>: movl $0x0,(%rax)
 PC (0x7fb58ab732cc) 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 audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video

Revision history for this message
mikgr (michel-groslier) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.