Bug 696844 - [abrt] deluge-daemon-1.3.1-2.fc14: std::_Rb_tree_increment: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] deluge-daemon-1.3.1-2.fc14: std::_Rb_tree_increment: Process /usr/bin/...
Keywords:
Status: CLOSED DUPLICATE of bug 659913
Alias: None
Product: Fedora
Classification: Fedora
Component: deluge
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fe751521c0962d56dfba0a3d9e3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 01:37 UTC by Jonathan Pritchard
Modified: 2011-11-28 17:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-28 17:47:10 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (77.88 KB, text/plain)
2011-04-15 01:37 UTC, Jonathan Pritchard 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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 ***
Note You need to log in before you can comment on or make changes to this bug.