WebKitPluginProcess crashed with SIGSEGV

Bug #1587703 reported by Swarnendu Biswas
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
New
Undecided
Unassigned

Bug Description

I experience this error/crash every time I use Web.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: libwebkit2gtk-4.0-37 2.12.3-1build0~xenial1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue May 31 22:40:01 2016
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess
InstallationDate: Installed on 2015-09-29 (245 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess 28 /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
SegvAnalysis:
 Segfault happened at: 0x7ff67b7b12ab: mov 0x38(%rcx),%r12
 PC (0x7ff67b7b12ab) ok
 source "0x38(%rcx)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: webkit2gtk
StacktraceTop:
 ?? () 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
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
Title: WebKitPluginProcess crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Swarnendu Biswas (swarna-cse) wrote :
Revision history for this message
Ubuntu GNOME (ug-bot) 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 #1575172, 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.