Bug 696844

Summary: [abrt] deluge-daemon-1.3.1-2.fc14: std::_Rb_tree_increment: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jonathan Pritchard <jonathanr.pritchard+bugzilla>
Component: delugeAssignee: Rahul Sundaram <metherid>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: calumlind, ggillies, justinnoah, metherid
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:fe751521c0962d56dfba0a3d9e3be4dd1a11234e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-28 17:47:10 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 Jonathan Pritchard 2011-04-15 01:37:20 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 79746 bytes
cmdline: /usr/bin/python /usr/bin/deluged --port=58846 --config=/home/Jon/.config/deluge
component: deluge
Attached file: coredump, 148598784 bytes
crash_function: std::_Rb_tree_increment
executable: /usr/bin/python
kernel: 2.6.35.11-83.fc14.i686.PAE
package: deluge-daemon-1.3.1-2.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302831407
uid: 500

How to reproduce
-----
1. Paused all torrents, then rebooted computer.
2. Attempted to start the deluge daemon running from the frontend
3. A brief spike in disk access and CPU usage, and then the daemon crashed.
Comment 1 Jonathan Pritchard 2011-04-15 01:37:23 UTC 
Created attachment 492258 [details]
File: backtrace
Comment 2 Calum 2011-11-28 17:47:10 UTC 

*** This bug has been marked as a duplicate of bug 659913 ***