WebKitWebProcess crashed with SIGSEGV in WebCore::GLContextGLX::~GLContextGLX()

Bug #1711838 reported by miguel loaiza ramirez
72
This bug affects 11 people
Affects Status Importance Assigned to Milestone
webkit2gtk (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Test Case:
1. Install and launch devhelp
2. Browse some documentation
3. Exit devhelp

Expected result
The app exits without a crash

Actual result
This crash

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libwebkit2gtk-4.0-37 2.17.91-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Aug 19 08:29:26 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess
InstallationDate: Installed on 2017-08-19 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 41
ProcEnviron:
 LANGUAGE=es_CR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_CR.UTF-8
 SHELL=/bin/bash
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
 __run_exit_handlers (status=0, listp=0x7f58519cc5d8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:83
Title: WebKitWebProcess crashed with SIGSEGV in __run_exit_handlers()
UpgradeStatus: Upgraded to artful on 2017-08-19 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
miguel loaiza ramirez (9uelo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 WebCore::GLContextGLX::~GLContextGLX (this=0x7f57e82c3000, __in_chrg=<optimized out>) at ./Source/WebCore/platform/graphics/glx/GLContextGLX.cpp:286
 WebCore::GLContextGLX::~GLContextGLX (this=0x7f57e82c3000, __in_chrg=<optimized out>) at ./Source/WebCore/platform/graphics/glx/GLContextGLX.cpp:294
 std::default_delete<WebCore::GLContext>::operator() (this=<optimized out>, __ptr=<optimized out>) at /usr/include/c++/7/bits/unique_ptr.h:78
 std::unique_ptr<WebCore::GLContext, std::default_delete<WebCore::GLContext> >::reset (__p=<optimized out>, this=0x7f57e8609fb8) at /usr/include/c++/7/bits/unique_ptr.h:376
 std::unique_ptr<WebCore::GLContext, std::default_delete<WebCore::GLContext> >::operator=(decltype(nullptr)) (this=0x7f57e8609fb8) at /usr/include/c++/7/bits/unique_ptr.h:312

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in webkit2gtk (Ubuntu):
importance: Undecided → Medium
summary: - WebKitWebProcess crashed with SIGSEGV in __run_exit_handlers()
+ WebKitWebProcess crashed with SIGSEGV in
+ WebCore::GLContextGLX::~GLContextGLX()
tags: removed: need-amd64-retrace
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
information type: Private Security → Public
description: updated
Revision history for this message
uklas (uklasius) wrote :

Can't help you more, because I DO NOT KNOW "HOW"! You must understand that i am JUST A COMMON USER, who tries hardly. Thank you for your patience & assistance.

Norbert (nrbrtx)
Changed in webkit2gtk (Ubuntu):
status: Confirmed → Incomplete
tags: removed: artful
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for webkit2gtk (Ubuntu) because there has been no activity for 60 days.]

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