Bug 1325445

Summary: [abrt] qt5-qtwebkit: load<int>(): QtWebProcess killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Max <maxpatera>
Component: qt5-qtwebkitAssignee: Than Ngo <than>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jgrulich, jreznik, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/215eceb56fd6dafeadb1cb83dee7a44abbea90d5
Whiteboard: abrt_hash:2d55e5cf83381d4a834e3ff2c8ebeea3a2f67578;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:47:47 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: 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 Max 2016-04-08 20:36:34 UTC 
Version-Release number of selected component:
qt5-qtwebkit-5.5.1-4.fc22

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/lib64/qt5/libexec/QtWebProcess 20
crash_function: load<int>
executable:     /usr/lib64/qt5/libexec/QtWebProcess
global_pid:     16690
kernel:         4.4.6-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 load<int> at ../../src/corelib/thread/qgenericatomic.h:90
 #1 load at ../../src/corelib/thread/qbasicatomic.h:118
 #2 next at ../../src/corelib/tools/qfreelist_p.h:233
 #3 QAbstractEventDispatcherPrivate::allocateTimerId at kernel/qabstracteventdispatcher.cpp:87
 #4 QAbstractEventDispatcher::registerTimer at kernel/qabstracteventdispatcher.cpp:252
 #5 QBasicTimer::start at kernel/qbasictimer.cpp:129
 #6 QNetworkAccessCache::updateTimer at access/qnetworkaccesscache.cpp:201
 #7 QNetworkAccessCache::timerEvent at access/qnetworkaccesscache.cpp:235
 #8 QObject::event at kernel/qobject.cpp:1261
 #9 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3716
Comment 1 Max 2016-04-08 20:36:39 UTC 
Created attachment 1145251 [details]
File: backtrace
Comment 2 Max 2016-04-08 20:36:40 UTC 
Created attachment 1145252 [details]
File: cgroup
Comment 3 Max 2016-04-08 20:36:41 UTC 
Created attachment 1145253 [details]
File: core_backtrace
Comment 4 Max 2016-04-08 20:36:42 UTC 
Created attachment 1145254 [details]
File: dso_list
Comment 5 Max 2016-04-08 20:36:43 UTC 
Created attachment 1145255 [details]
File: environ
Comment 6 Max 2016-04-08 20:36:44 UTC 
Created attachment 1145256 [details]
File: limits
Comment 7 Max 2016-04-08 20:36:45 UTC 
Created attachment 1145257 [details]
File: maps
Comment 8 Max 2016-04-08 20:36:45 UTC 
Created attachment 1145258 [details]
File: mountinfo
Comment 9 Max 2016-04-08 20:36:46 UTC 
Created attachment 1145259 [details]
File: namespaces
Comment 10 Max 2016-04-08 20:36:47 UTC 
Created attachment 1145260 [details]
File: open_fds
Comment 11 Max 2016-04-08 20:36:48 UTC 
Created attachment 1145261 [details]
File: proc_pid_status
Comment 12 Max 2016-04-08 20:36:49 UTC 
Created attachment 1145262 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:47:47 UTC 
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.