Bug 758222

Summary: [abrt] komparator-0.9-4.fc12: KFileItemExt::~KFileItemExt: Process /usr/bin/komparator was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: dweb98
Component: komparatorAssignee: Neal Becker <ndbecker2>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: ndbecker2
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:3088e061316ca5d7d3821b2338cd01b2003d3a76
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-29 15:31:55 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

Description dweb98 2011-11-29 15:06:38 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 141263 bytes
cmdline: komparator
component: komparator
Attached file: coredump, 741060608 bytes
crash_function: KFileItemExt::~KFileItemExt
executable: /usr/bin/komparator
kernel: 2.6.35.14-103.fc14.i686
package: komparator-0.9-4.fc12
rating: 4
reason: Process /usr/bin/komparator was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1322578971
uid: 500

comment
-----
1. Started a Directory Search. 
2.It was taking too long and using too much System Recorces.
3.Canceled and it Crashed.

How to reproduce
-----
1.Started a Directory Search. 
2.It was taking too long and using too much System Recorces.
3.Canceled and it Crashed.
Comment 1 dweb98 2011-11-29 15:06:40 UTC 
Created attachment 538040 [details]
File: backtrace
Comment 2 Neal Becker 2011-11-29 15:31:55 UTC 
Reported upstream:

https://sourceforge.net/tracker/?group_id=156901&atid=801643