Bug 1284151

Summary: [abrt] webkitgtk4: _g_log_abort(): WebKitWebProcess killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Erick Omar Delgado <edelgado81>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: ajax, edelgado81, fschwarz, ignatenko, klember, liedekef, mcatanzaro+wrong-account-do-not-cc, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/70b494cbdace83bf07e45f8ce6daf2b97172a498
Whiteboard: abrt_hash:31a4fcdaa9b176f5e04d1abcd050d04763b47579;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-14 08:08:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description Erick Omar Delgado 2015-11-21 03:58:17 UTC
Version-Release number of selected component:
webkitgtk4-2.10.4-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 27
crash_function: _g_log_abort
executable:     /usr/libexec/webkit2gtk-4.0/WebKitWebProcess
global_pid:     5153
kernel:         4.2.6-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _g_log_abort at gmessages.c:324
 #8 DRI2GetBuffersWithFormat at dri2.c:491
 #9 dri2GetBuffersWithFormat at dri2_glx.c:900
 #10 dri2_drawable_get_buffers at dri2.c:213
 #11 dri2_allocate_textures at dri2.c:407
 #12 dri_st_framebuffer_validate at dri_drawable.c:83
 #13 st_framebuffer_validate at state_tracker/st_manager.c:200
 #14 st_api_make_current at state_tracker/st_manager.c:774
 #15 dri_make_current at dri_context.c:245
 #16 driBindContext at dri_util.c:530

Comment 1 Erick Omar Delgado 2015-11-21 03:58:21 UTC
Created attachment 1097424 [details]
File: backtrace

Comment 2 Erick Omar Delgado 2015-11-21 03:58:22 UTC
Created attachment 1097425 [details]
File: cgroup

Comment 3 Erick Omar Delgado 2015-11-21 03:58:23 UTC
Created attachment 1097426 [details]
File: core_backtrace

Comment 4 Erick Omar Delgado 2015-11-21 03:58:24 UTC
Created attachment 1097427 [details]
File: dso_list

Comment 5 Erick Omar Delgado 2015-11-21 03:58:25 UTC
Created attachment 1097428 [details]
File: environ

Comment 6 Erick Omar Delgado 2015-11-21 03:58:26 UTC
Created attachment 1097429 [details]
File: limits

Comment 7 Erick Omar Delgado 2015-11-21 03:58:28 UTC
Created attachment 1097430 [details]
File: maps

Comment 8 Erick Omar Delgado 2015-11-21 03:58:29 UTC
Created attachment 1097431 [details]
File: mountinfo

Comment 9 Erick Omar Delgado 2015-11-21 03:58:30 UTC
Created attachment 1097432 [details]
File: namespaces

Comment 10 Erick Omar Delgado 2015-11-21 03:58:31 UTC
Created attachment 1097433 [details]
File: open_fds

Comment 11 Erick Omar Delgado 2015-11-21 03:58:32 UTC
Created attachment 1097434 [details]
File: proc_pid_status

Comment 12 Franky Van Liedekerke 2015-12-31 10:07:01 UTC
Another user experienced a similar problem:

Closing a tab in the browser caused this.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 24
crash_function: _g_log_abort
executable:     /usr/libexec/webkit2gtk-4.0/WebKitWebProcess
global_pid:     2981
kernel:         4.2.8-300.fc23.x86_64
package:        webkitgtk4-2.10.4-1.fc23
reason:         WebKitWebProcess killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 13 Michael Catanzaro 2016-03-02 00:05:03 UTC
Can either of you reproduce this issue somehow? Unfortunately the bug report is not actionable, we need a backtrace taken when running with GDK_SYNCHRONIZE to get anything meaningful:

"""
(Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
"""

Comment 14 Michael Catanzaro 2016-03-02 00:06:14 UTC
(Was planning to move this to mesa, before I noticed the X error; I suspect that's somehow our fault....)

Comment 15 Michael Catanzaro 2016-03-02 00:34:33 UTC
Eh, I'll move this back to mesa after all, it's too deep in graphics driver land for me to feel comfortable reporting this as a WebKit bug....

Comment 16 Erick Omar Delgado 2016-05-17 03:11:28 UTC
(In reply to Michael Catanzaro from comment #13)
> Can either of you reproduce this issue somehow? Unfortunately the bug report
> is not actionable, we need a backtrace taken when running with
> GDK_SYNCHRONIZE to get anything meaningful:
> 
> """
> (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the GDK_SYNCHRONIZE environment
>    variable to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error() function.)
> """

I will try to reproduce this issue.

Comment 17 Igor Gnatenko 2016-09-14 08:08:49 UTC
I hope this has been resolved already, if not - please reopen bug.