Bug 1325700

Summary: [abrt] webkitgtk4: pthread_cond_timedwait@@GLIBC_2.3.2(): WebKitPluginProcess2 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: webkitgtk4Assignee: Tomas Popela <tpopela>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: klember, mcatanzaro+wrong-account-do-not-cc, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ab13d070715e03c9680a05bffd0567b1ba239fe6
Whiteboard: abrt_hash:cde862efef82efd7e39411c1c72818ba997b2730;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-10 21:27:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Joachim Frieben 2016-04-10 18:38:03 UTC 
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
Comment 1 Joachim Frieben 2016-04-10 18:38:07 UTC 
Created attachment 1145732 [details]
File: backtrace
Comment 2 Joachim Frieben 2016-04-10 18:38:09 UTC 
Created attachment 1145733 [details]
File: cgroup
Comment 3 Joachim Frieben 2016-04-10 18:38:10 UTC 
Created attachment 1145734 [details]
File: core_backtrace
Comment 4 Joachim Frieben 2016-04-10 18:38:12 UTC 
Created attachment 1145735 [details]
File: dso_list
Comment 5 Joachim Frieben 2016-04-10 18:38:13 UTC 
Created attachment 1145736 [details]
File: environ
Comment 6 Joachim Frieben 2016-04-10 18:38:14 UTC 
Created attachment 1145737 [details]
File: exploitable
Comment 7 Joachim Frieben 2016-04-10 18:38:16 UTC 
Created attachment 1145738 [details]
File: limits
Comment 8 Joachim Frieben 2016-04-10 18:38:18 UTC 
Created attachment 1145739 [details]
File: maps
Comment 9 Joachim Frieben 2016-04-10 18:38:19 UTC 
Created attachment 1145740 [details]
File: mountinfo
Comment 10 Joachim Frieben 2016-04-10 18:38:20 UTC 
Created attachment 1145741 [details]
File: namespaces
Comment 11 Joachim Frieben 2016-04-10 18:38:21 UTC 
Created attachment 1145742 [details]
File: open_fds
Comment 12 Joachim Frieben 2016-04-10 18:38:23 UTC 
Created attachment 1145743 [details]
File: proc_pid_status
Comment 13 Joachim Frieben 2016-04-10 18:38:24 UTC 
Created attachment 1145744 [details]
File: var_log_messages
Comment 14 Michael Catanzaro 2016-04-10 21:27:19 UTC 
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.)