WebKitWebProcess crashed with SIGSEGV

Bug #1717804 reported by Paolo Astengo
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
webkit2gtk (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libwebkit2gtk-4.0-37 2.18.0-2
Uname: Linux 4.13.2-041302-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 17 19:28:35 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
InstallationDate: Installed on 2016-05-20 (484 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 46
SegvAnalysis:
 Segfault happened at: 0x7fbf2892c6dd: mov 0x14(%rsi),%r9d
 PC (0x7fbf2892c6dd) ok
 source "0x14(%rsi)" (0x300000016) not located in a known VMA region (needed readable region)!
 destination "%r9d" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: webkit2gtk
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
 () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
Title: WebKitWebProcess crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin netdev pico plugdev sambashare sudo

Revision history for this message
Paolo Astengo (p-astengo) wrote :
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in webkit2gtk (Ubuntu):
status: New → Confirmed
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.