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
Created attachment 1097424 [details] File: backtrace
Created attachment 1097425 [details] File: cgroup
Created attachment 1097426 [details] File: core_backtrace
Created attachment 1097427 [details] File: dso_list
Created attachment 1097428 [details] File: environ
Created attachment 1097429 [details] File: limits
Created attachment 1097430 [details] File: maps
Created attachment 1097431 [details] File: mountinfo
Created attachment 1097432 [details] File: namespaces
Created attachment 1097433 [details] File: open_fds
Created attachment 1097434 [details] File: proc_pid_status
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
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.) """
(Was planning to move this to mesa, before I noticed the X error; I suspect that's somehow our fault....)
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....
(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.
I hope this has been resolved already, if not - please reopen bug.