#24 closed bug (Fixed)
Segfault in deluge_core.so while checking partial download (Debian)
Reported by: | debbugs6@alistairphipps.com | Owned by: | markybob |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | 0.5.x | Version: | 0.5.8.3 |
Keywords: | crash segfault deluge_core.so | Cc: |
Description
Torrent partially downloaded; ran out of disk space; killed deluge forcefully (ctrl-alt-backspace to kill X). Added disk space to partition and resumed deluge. On startup, deluge started to check the partial download. It reproducibly crashes part way through the check. Here is the backtrace:
#0 0xb6c9995d in libtorrent::piece_manager::export_piece_map ()
from /var/lib/python-support/python2.4/deluge/deluge_core.so No symbol table info available.
#1 0xb6c04bed in libtorrent::torrent_handle::write_resume_data ()
from /var/lib/python-support/python2.4/deluge/deluge_core.so No symbol table info available.
#2 0xb6d571c1 in ?? ()
from /var/lib/python-support/python2.4/deluge/deluge_core.so No symbol table info available.
... Appears to be the same as this Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/deluge-torrent/+bug/190028
I have also filed this as Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465059
Change History (3)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
i think this is fixed in svn (http://code.rasterbar.com/libtorrent/ticket/252). let us know and reopen if not
How many torrents did you have in your session? Just the one being checked? What allocation method are you using? Compact or Full?