Version-Release number of selected component: webkitgtk4-2.8.5-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 19 crash_function: bcmdec_mul_inst_cor executable: /usr/libexec/webkit2gtk-4.0/WebKitWebProcess global_pid: 11935 kernel: 4.1.6-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 bcmdec_mul_inst_cor at gstbcmdec.c:2235 #1 gst_bcm_dec_change_state at gstbcmdec.c:869 #2 gst_element_change_state at gstelement.c:2602 #3 gst_element_set_state_func at gstelement.c:2558 #4 connect_pad at gstdecodebin2.c:2095 #5 analyze_new_pad at gstdecodebin2.c:1742 #6 pad_added_cb at gstdecodebin2.c:2585 #7 caps_notify_cb at gstdecodebin2.c:2695 #13 gst_object_dispatch_properties_changed at gstobject.c:445 #14 g_object_notify_by_spec_internal at gobject.c:1149
Created attachment 1068478 [details] File: backtrace
Created attachment 1068479 [details] File: cgroup
Created attachment 1068480 [details] File: core_backtrace
Created attachment 1068481 [details] File: dso_list
Created attachment 1068482 [details] File: environ
Created attachment 1068483 [details] File: limits
Created attachment 1068484 [details] File: maps
Created attachment 1068485 [details] File: mountinfo
Created attachment 1068486 [details] File: namespaces
Created attachment 1068487 [details] File: open_fds
Created attachment 1068488 [details] File: proc_pid_status
Created attachment 1068489 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.