Hide Forgot
Version-Release number of selected component: webkitgtk4-2.10.9-1.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess2 12 /usr/lib64/mozilla/plugins/libflashplayer.so crash_function: pthread_cond_timedwait@@GLIBC_2.3.2 executable: /usr/libexec/webkit2gtk-4.0/WebKitPluginProcess2 global_pid: 3313 kernel: 4.4.6-301.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 4 (5 frames) #0 pthread_cond_timedwait@@GLIBC_2.3.2 at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 __gthread_cond_timedwait at /usr/include/c++/5.3.1/x86_64-redhat-linux/bits/gthr-default.h:871 #2 std::condition_variable::__wait_until_impl<std::chrono::duration<long, std::ratio<1l, 1000000000l> > > at /usr/include/c++/5.3.1/condition_variable:165 #3 std::condition_variable::wait_until<std::chrono::duration<long, std::ratio<1l, 1000000000l> > > at /usr/include/c++/5.3.1/condition_variable:105 #4 std::_V2::condition_variable_any::wait_until<std::unique_lock<bmalloc::Mutex>, std::chrono::_V2::system_clock, std::chrono::duration<long, std::ratio<1l, 1000000000l> > > at /usr/include/c++/5.3.1/condition_variable:273
Created attachment 1145732 [details] File: backtrace
Created attachment 1145733 [details] File: cgroup
Created attachment 1145734 [details] File: core_backtrace
Created attachment 1145735 [details] File: dso_list
Created attachment 1145736 [details] File: environ
Created attachment 1145737 [details] File: exploitable
Created attachment 1145738 [details] File: limits
Created attachment 1145739 [details] File: maps
Created attachment 1145740 [details] File: mountinfo
Created attachment 1145741 [details] File: namespaces
Created attachment 1145742 [details] File: open_fds
Created attachment 1145743 [details] File: proc_pid_status
Created attachment 1145744 [details] File: var_log_messages
Looks like a plugin process crash deep in Adobe Flash; can't do anything about that obviously. (The truncated backtrace in comment #0 seems to be for the wrong thread.)