WebKitWebProcess crashed with SIGSEGV

Bug #1922356 reported by corrado venturini
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webkit2gtk (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu just installed from: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402)
Open 'Help' Ubuntu Desktop Guide, click on 'Getting started with GNOME' ... crash

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: libwebkit2gtk-4.0-37 2.31.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 2 13:55:31 2021
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
ExecutableTimestamp: 1616757812
InstallationDate: Installed on 2021-04-02 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 8 27
ProcCwd: /home/corrado
SegvAnalysis:
 Segfault happened at: 0x7fd8001fd035: cmpl $0x10000,(%rsi)
 PC (0x7fd8001fd035) ok
 source "$0x10000" ok
 destination "(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: webkit2gtk
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
Title: WebKitWebProcess crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo whoopsie
separator:

Revision history for this message
corrado venturini (corradoventu) wrote :
information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
corrado venturini (corradoventu) wrote :

Problem disappeared after upgrades.

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.