Bug 1108920

Summary: [abrt] ktorrent: _xend(): ktorrent killed by SIGSEGV
Product: [Fedora] Fedora Reporter: ppaglial
Component: ktorrentAssignee: Roland Wolters <roland.wolters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alekcejk, ppaglial, rdieter, roland.wolters, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/32a83f95731a7789d950311c596a879a4689aaa2
Whiteboard: abrt_hash:7bbd5af6e80482ca9abbff89c557ba3ccce7e23b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 21:05:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description ppaglial 2014-06-12 20:48:16 UTC
Version-Release number of selected component:
ktorrent-4.3.1-4.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/ktorrent -session 10d9cfe4e4000139657297000000016050042_1402537912_536086
crash_function: _xend
executable:     /usr/bin/ktorrent
kernel:         3.14.5-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _xend at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:33
 #1 __lll_unlock_elision at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
 #2 unlock at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1245
 #3 ~CacheLocker at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1317
 #4 KSharedDataCache::find at /usr/src/debug/kdelibs-4.12.5/kdecore/util/kshareddatacache.cpp:1608
 #5 KIconLoaderPrivate::findCachedPixmapWithPath at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconloader.cpp:854
 #6 KIconLoader::loadIcon at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconloader.cpp:1123
 #7 KIconEngine::pixmap at /usr/src/debug/kdelibs-4.12.5/kdeui/icons/kiconengine.cpp:104
 #8 QIcon::pixmap at image/qicon.cpp:684
 #9 QWidgetPrivate::setWindowIcon_sys at kernel/qwidget_x11.cpp:1490

Comment 1 ppaglial 2014-06-12 20:48:21 UTC
Created attachment 908294 [details]
File: backtrace

Comment 2 ppaglial 2014-06-12 20:48:23 UTC
Created attachment 908295 [details]
File: cgroup

Comment 3 ppaglial 2014-06-12 20:48:24 UTC
Created attachment 908296 [details]
File: core_backtrace

Comment 4 ppaglial 2014-06-12 20:48:26 UTC
Created attachment 908297 [details]
File: dso_list

Comment 5 ppaglial 2014-06-12 20:48:28 UTC
Created attachment 908298 [details]
File: environ

Comment 6 ppaglial 2014-06-12 20:48:30 UTC
Created attachment 908299 [details]
File: exploitable

Comment 7 ppaglial 2014-06-12 20:48:32 UTC
Created attachment 908300 [details]
File: limits

Comment 8 ppaglial 2014-06-12 20:48:33 UTC
Created attachment 908301 [details]
File: maps

Comment 9 ppaglial 2014-06-12 20:48:35 UTC
Created attachment 908302 [details]
File: open_fds

Comment 10 ppaglial 2014-06-12 20:48:36 UTC
Created attachment 908303 [details]
File: proc_pid_status

Comment 11 ppaglial 2014-06-12 20:48:38 UTC
Created attachment 908304 [details]
File: var_log_messages

Comment 12 Roland Wolters 2014-06-16 09:47:44 UTC
Thanks for your bug report. Can you give any further information when the bug struck you? Can you reproduce the crash, or did it happen only once?

Comment 13 Rex Dieter 2014-06-16 11:58:34 UTC
It looks like a corrupted icon/pixmap cache (which can happen when disk space runs low, or under memory pressure when using default tmpfs /var/tmp)

Comment 14 Rex Dieter 2014-06-16 12:01:37 UTC
See also upstream report,
https://bugs.kde.org/show_bug.cgi?id=305654
(assuming I'm correct, the backtrace is similar but not exactly the same)

Comment 15 ppaglial 2014-06-17 12:30:27 UTC
The crash happened at startup. I don't think it is a memory issue, as I have 16 GB of RAM and plenty of disk space. Lately I am experiencing crashes of various applications right at startup.

Comment 16 Roland Wolters 2014-06-17 13:08:52 UTC
Thanks for the details. But what I failed to understand so far is: does this happen every time at startup of Ktorrekt? Or did the crash occur only once?

And, since you mentioned that you have various apps crashing: have you run a memory check? Maybe one of your memory banks is faulty?

Comment 17 ppaglial 2014-06-17 17:50:08 UTC
Thank you for your reply. I often have random applications crashing at startup, when I first login after powering up. You made a good point with a possible faulty RAM, so I ran a memory check with memtester (12000 MB, 3 loops) and everything is OK. I think this was the first time ktorrent crashed. I had not even opened it.

Comment 18 Roland Wolters 2014-06-18 16:43:10 UTC
It is hard to debug a random crash. Please keep us up2date if another crash occurs and send us the debug ouput. If the debug output is similar it should be much easier to get to the core of the problem...

Comment 19 ppaglial 2014-07-10 15:16:39 UTC
I have been monitoring this for a while. Ktorrent hasn't crashed again to date. I still have crashes at startup, randomly. The most frequent one seems to be kde.

Comment 20 Fedora End Of Life 2015-05-29 12:06:03 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 21 Fedora End Of Life 2015-06-29 21:05:52 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.